Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it possible to cause the reimport of a single Git-based OSV record #2018

Open
andrewpollock opened this issue Feb 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@andrewpollock
Copy link
Contributor

Problem statement:

Today, it is not possible to cause the reimport (and re-enumeration) of a single record in a Git-based OSV record source.
The best option (as opposed to setting last_synced_hash to null for the given source record in SourceRepository in Datastore, and causing a full reimport) is to determine the commit before the commit that added/modified the record of interest in the Git repository, and reset last_synced_hash to that commit hash. Depending on how far back in time this is, the amount of unnecessary reprocessing is significant (although this will be less relevant once #2017 is implemented, and if the interval there is sufficiently short it will reduce the need for this to be addressed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant