feat: store timestamp of last change of given repository #1049
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.
Description
Lets store the last change of every repository done by vmaas. So that in vmaas-sync for Patch/Vulnerability, we can use this timestamp instead of "revision" timestamp for
modified_since
parameter. Since the revision timestamp is not in "our hands" to modify and by this new timestamp we can detect timestamp when repo changed in vmaas (and not in RedHat CDN).Secure Coding Practices Checklist GitHub Link
Secure Coding Checklist