docs: enhancing documentation for trivyignore #4814
Conversation
Signed-off-by: AnaisUrlichs <[email protected]>
| @@ -215,6 +215,12 @@ generic-unwanted-rule | |||
| aws-account-id | |||
| ``` | |||
|
|
|||
| For a container image, such as the one used below, follow these steps to add a vulnerability to the `trivyignore` file: | |||
There was a problem hiding this comment.
What kind of comments did we get? It just adds CVE-ID to .trivyignore. Why do we want to navigate users to AVD?
There was a problem hiding this comment.
Well people were pointing out that the steps are not documented -- so without documentation I cannot know what is wrong with the existing documentation -- if you think this is unnecessary, then we can leave it
There was a problem hiding this comment.
I'm wondering if they wanted to know how to ignore misconfiguration findings. Ignoring vulnerabilities is too simple. When CVE-2019-1563 is detected, and they want to ignore it, they just add it to .trivyignore. There are no special steps to explain.
We should clarify what is unclear for people in our documentation.
|
Closing this pull request for now |
There were some comments asking for better documentation on how to set up the trivyignore file