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

feat(misconfig): Load misconfiguration specs from bundles #7138

Closed
simar7 opened this issue Jul 10, 2024 · 0 comments · Fixed by #7179
Closed

feat(misconfig): Load misconfiguration specs from bundles #7138

simar7 opened this issue Jul 10, 2024 · 0 comments · Fixed by #7179
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning
Milestone

Comments

@simar7
Copy link
Member

simar7 commented Jul 10, 2024

Today we load misconfiguration specs via the trivy-checks dependency as described here.

Since now specs are shipped along with the Trivy checks bundle, we can improve this experience by loading them from the bundle first. In case of any errors, we can fall back to the existing mechanism of loading from the trivy-checks library. This experience will be similar to the one we have with checks today.

The benefit of this approach being that we will be able to decouple the distribution of specs from the release of Trivy, just as how we have done with misconfiguration checks.

@simar7 simar7 self-assigned this Jul 10, 2024
@simar7 simar7 added this to the v0.54.0 milestone Jul 10, 2024
@simar7 simar7 added kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning labels Jul 10, 2024
@DmitriyLewen DmitriyLewen modified the milestones: v0.54.0, v0.55.0 Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants