feat: move Vanir signature generation to a cron job#5126
Draft
cuixq wants to merge 14 commits intogoogle:masterfrom
Draft
feat: move Vanir signature generation to a cron job#5126cuixq wants to merge 14 commits intogoogle:masterfrom
cuixq wants to merge 14 commits intogoogle:masterfrom
Conversation
Contributor
Author
|
/gemini review |
Contributor
Author
|
/gemini review |
This file contains hidden or 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
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.
#4611
This PR introduces a new
vanir_signaturesworker to enrich OSV records with Vanir signatures. This cron job identifies modified vulnerabilities, generates the signatures, and updates both the Datastore and GCS with the enriched data.database_specificfield.database_specificfield of affected packages.--dry-runflag and--output-diroption for testing and inspection of generated signatures without modifying production data.