This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
Initial version of the containerinfo object, state and item XSD #147
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.
Request for comments.
I am designing a new OVAL test that queries container image properties. There are two main uses cases of such a test:
Personally I am more interested in the first use-case but I want to make the test powerful enough to satisfy both.
Example workflow for the container image CVE feed workflow:
This is very similar to the RPM CVE feed workflow. My main issue is how to make this vendor neutral and generic, especially the part about combining Version and Release labels. Other vendors may do this in other ways, these two particular labels don't even have to be present. At the same time I need a simple way to do the piece-wise comparison, a lexical comparison won't do. Any ideas here are welcome.