DNM: feat(adv/validate): check for package config existing #989
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 introduces a new advisory validation check to make sure each advisory document describes a package that's currently defined in the corresponding package repo (e.g. in
wolfi-dev/os
, if the advisories repo iswolfi-dev/advisories
).The goal is to help us move toward a state where each defined package has only one advisory document across the universe of advisory data. This will make it easier for us to unify all advisory data into a single repo. And before that point, it also helps ensure we don't have duplicate or stale data that can leak into our various downstream data artifacts (e.g. the secdb, the OSV feed, and other export destinations).
Left to do: