You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trivy has moved to deprecate the "slow" flag in favor of "parallel", as such we should start transitioning away from the "slow" flag. However, there is a question of backwards compatibility. For the PR that introduces "parallel", should "slow" be retained as a configuration option that maps to a default "parallel" setting or should "slow" be stripped completely?
Additionally, in the upcoming v0.55.0 Trivy will be introducing the "detection-priority" flag (reference: aquasecurity/trivy#7198) that we should expose as configurable in the Helm chart.
The text was updated successfully, but these errors were encountered:
Trivy has moved to deprecate the "slow" flag in favor of "parallel", as such we should start transitioning away from the "slow" flag. However, there is a question of backwards compatibility. For the PR that introduces "parallel", should "slow" be retained as a configuration option that maps to a default "parallel" setting or should "slow" be stripped completely?
Additionally, in the upcoming v0.55.0 Trivy will be introducing the "detection-priority" flag (reference: aquasecurity/trivy#7198) that we should expose as configurable in the Helm chart.
The text was updated successfully, but these errors were encountered: