-
Notifications
You must be signed in to change notification settings - Fork 30
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
Omit the trivy DB schema version for backwards compatibility with trivy < 0.50.0 #1063
Omit the trivy DB schema version for backwards compatibility with trivy < 0.50.0 #1063
Conversation
…vy < 0.50.0 Fixes: cert-manager#1062 (comment) Signed-off-by: Richard Wall <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: inteon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@wallrj: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
In #1062 (comment) @inteon noticed that the trivy tests were now failing on cert-manager 1.12 and 1.14 branches.
Those releases use an older version of trivy < 0.50.0 which unconditionally appends the schema version (tag) to the supplied DB registry.
Newer versions of trivy >= 0.50.0, only append the schema version if it has not been supplied, and log a backwards compatibility message in that case:
trivy-db
andtrivy-java-db
registries by default aquasecurity/trivy#6219 (v0.50.0)So to support both old and new versions, I've removed the schema version from the DB registry variable.
Testing
I ran trivy on all the release branches and observed it download the DB successfully: