-
Notifications
You must be signed in to change notification settings - Fork 98
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
[DRAFT] Exclude vulnerabilities by CSV from image scan assesments. #1495
[DRAFT] Exclude vulnerabilities by CSV from image scan assesments. #1495
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some initial comments.
I can wait until you and Chris sync up and you get a chance to fill in the rest of it before I do another pass over the PR.
4f459e8
to
48f4a88
Compare
5610d82
to
d5bcd0b
Compare
@davido-tigera I think the general approach here is sound. I still think the feature is weak where it comes to creating the CSV file. It's not great to have a bunch of tables and explanatory information inside a step procedure. You might consider chunking this more clearly into "Creating your CSV file" and "Uploading the CSV for bulk exceptions". @stevegaossou will be able to continue with the final reviews and merges. If it merges before I'm back, I'll be sure to look it over and talk to you then if I have any more suggestions. |
d5bcd0b
to
17e9a65
Compare
|
||
Upload the formatted CSV: | ||
|
||
1. TODO write this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stevegaossou , there is a TODO here. My suggestion:
- Go to Image Assurance, Vulnerability Exceptions.
- Click on the top-right arrow-shaped button (Upload exceptions).
- Follow the instructions provided in the pop-up modal to create the vulnerability exceptions.
4. Open the exported CSV file in your preferred editor. | ||
5. Add two columns: **Justification** and **Scope**. | ||
|
||
The **Scope** column can have three values: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stevegaossou , a kind reminder to update these values to any, repo and image
Closing here, moving changes to #1539. |
To run locally, do:
nvm use stable
chmod +x ./scripts/cc-next-preview-config.sh
./scripts/cc-next-preview-config.sh
make start