Skip to content
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

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

Closed
simar7 opened this issue Aug 7, 2024 · 0 comments · Fixed by #7776
Closed

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

simar7 opened this issue Aug 7, 2024 · 0 comments · Fixed by #7776
Assignees
Labels
kind/breaking Categorizes issue or PR as related to breaking compatibility. scan/misconfiguration Issues relating to misconfiguration scanning
Milestone

Comments

@simar7
Copy link
Member

simar7 commented Aug 7, 2024

It's reasonable to drop support for Exceptions since:

  1. 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.
  2. 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 simar7 added the kind/breaking Categorizes issue or PR as related to breaking compatibility. label Aug 7, 2024
@simar7 simar7 self-assigned this Sep 10, 2024
@simar7 simar7 added this to the v0.56.0 milestone Sep 10, 2024
@simar7 simar7 added the scan/misconfiguration Issues relating to misconfiguration scanning label Sep 12, 2024
@simar7 simar7 modified the milestones: v0.56.0, v0.57.0 Sep 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/breaking Categorizes issue or PR as related to breaking compatibility. scan/misconfiguration Issues relating to misconfiguration scanning
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

1 participant