-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ubuntu: verify dist is actually ubuntu #970
Conversation
@crozzy the unit tests pass, but I'm wondering how you usually test ClairCore upgrades because I haven't done it before. Any suggestions? |
I usually do a manual test for instances like these, we currently don't have a good automated way to test changes on environments with existing state:
Happy to go into more detail if any steps aren't clear |
This looks good, just needs a rebase |
Testing by doing the following:
From here, I can see the following:
One thing to note: the vuln report only mentioned Debian in the distributions map. Never mentioned Ubuntu. For example:
Looks like this PR properly attributes these images to Debian, only. |
nice work @RTann |
65fdc77
to
14a482d
Compare
14a482d
to
e2a0ae7
Compare
Signed-off-by: RTann <[email protected]>
e2a0ae7
to
c9c47ca
Compare
This PR addresses #969
Note: This PR does not address potentially needing to migrate/cleanup the database for current installations. This does, however, prevent the issue from popping up in fresh installs.