wip: switch to invoking yardstick validate from within grype-db python #371
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is put up to contrast with a CLI invocation of yardstick, which might be preferable. Signed-off-by: Will Murphy <[email protected]>
This was referenced Aug 30, 2024
|
Replaced by #373 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is put up to contrast with a CLI invocation of yardstick, which might be preferable.
This is one approach to bringing anchore/yardstick#380 into grype-db. A separate would be to remove the
db validatecommand entirely fromgrype-db-manager. I'll probably explore that in a separate PR.