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.

Sign up for GitHub

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

Jump to bottom

BREAKING(report): Drop support for `EXCEPTIONS` from results #7314

Open

simar7 opened this issue Aug 7, 2024 · 0 comments

Assignees

Labels

kind/breaking scan/misconfiguration

Milestone

Member

simar7 commented Aug 7, 2024 •

edited

Loading

It's reasonable to drop support for Exceptions since:

No other scanner uses it today. So the concept of Exceptions only exists in misconfiguration scanning. I believe the original concept originated from conftest but we have diverged quite a bit from that now in Trivy.
The fact that it isn't very useful once we start to hide misconfigurations, if they are ignored.

~~It will obviously be a breaking change that we will need to announce.~~

Relevant discussion #7474

Originally posted by @simar7 in #7171 (comment)

simar7 mentioned this issue

fix(report): hide empty table when all secrets/license/misconfigs are ignored #7171

Merged

7 tasks

simar7 added the kind/breaking label

simar7 self-assigned this

simar7 added this to the v0.56.0 milestone

simar7 added the scan/misconfiguration label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment