Closed DmitriyLewen closed 1 week ago
This is critical for us.
We are delaying the release of v0.55.0
until this issue is resolved.
This is due two reasons:
(short term fix): There is a performance issue in OPA. See here for the issue. We have a fix for it upstream but it hasn't been merged just yet. In the meantime, we can cherry pick the fix to not delay our release as done here
(long term fix, separate issue) As @knqyf263 mentioned here we should only initialize the misconf checks when the misconfiguration scanner is enabled. We will tackle this improvement in a separate feature improvement so we don't delay the current release. Issue to track https://github.com/aquasecurity/trivy/issues/7434
Description
After #7417 Trivy starts slower.