fix: make PURLs use oci type / include architecture in --source-version
#448
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.
Same thing as stackabletech/actions#11, but for our operator images. It probably makes sense for the same person to review both this PR and the other.
Use OCI type for PURLs, according to https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#oci
This is more correct in general and most importantly makes the PURL equal to the one Trivy generates for our container images.
Hint: To check the PURL Trivy generates, run for example these commands:
The second commit includes the architecture in the component version in the SBOM (
0.0.0-dev-amd64
instead of0.0.0-dev
). That is in line with the image tag and we also do it this way with our product images.