This repository was archived by the owner on Jan 27, 2023. It is now read-only.
Filter packages that are "owned" by other packages #917
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.
What this PR does / why we need it:
Today engine will perform vulnerability matching for all packages discovered within a image, even if a given package is really "owned" by a parent package (e.g. An RPM has packaged within it a Python wheel that gets installed, the RPM is the "owner" of the wheel package). In these cases the parent package should be used for vulnerability matching and the child should be ignored (see #315 , #445 , and #460).
This PR bumps the syft version that labels relations between packages + adds a filter to the SBOM report to exclude packages that are owned by other packages.
Additionally this PR allows for additional attributes on image import, enabling schema additions to not cause a 400 to be returned.
Which issue this PR fixes
Fixes #445 , Fixes #460
Tasks:
anchore-cli image add ...)