Remove providers' pull information from DB metadata file #1846
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
wagoodman
approved these changes
May 6, 2024
…)" This reverts commit 4584423. Signed-off-by: Arvind Somya <arvind.somya@anchore.com>
asomya
force-pushed
the
revert-1795-ENTERPRISE-3667
branch
from
d97fc93
to
9d9c0be
Compare
wagoodman
changed the title
This was referenced May 7, 2024
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.
Reverts #1795
We'd like to carry forward more information from vunnel (upstream of grype-db) to convey to grype DB consumers more details about the status and origin of the underlying data. #1795 started by adding a timestamp each each upstream provider was refreshed, a purely additive change, so it was added to the current v5 schema. However we've had reports of consumers that were adversely affected by this change, so we've decided to hold off on a change to the metadata.json datashape in the mean time. This will most likely be added as a separate file in a future change, and migrated back to the metadata.json when the DB schema is bumped -- but all of that will be finalized later.