feat: trivy should not fail if one rego policy fails #4183
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
scan/misconfiguration
Issues relating to misconfiguration scanning
Today trivy fails out on a scan even if one policy has an issue. An example of this is here: #4124
We should handle this more gracefully, for instance show an error to the user about the failing policy and continue with scanning the rest of the policies.
The text was updated successfully, but these errors were encountered: