Replies: 2 comments
-
Yes, I can't seem to find the previous discussion that we had in general regarding Trivy's behavior when supplied user input isn't valid/missing. But I think in general, we should warn or inform the user about such a situation so that the scan results or Trivy's behavior isn't questioned. |
Beta Was this translation helpful? Give feedback.
0 replies
-
We already have an issue to track this #7093 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
Not a critical issue but when using
--ignorefile badpath.yaml
with an invalid path, Trivy silently ignores the error. I think it should result in an error or a warning. For reference, the simlar flag--ignore-policy
will not just error but also stop trivy.Target
None
Scanner
None
Beta Was this translation helpful? Give feedback.
All reactions