Cache TrivyDB for 24hrs #1227
Closed
Cache TrivyDB for 24hrs #1227
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
* Combined both docker workflows into one because they do the same thing
DrizzlyOwl
force-pushed
the
patch/trivy-workflow
branch
from
693f3f1 to
8a2546b
Compare
mshakirdfe
approved these changes
Dec 2, 2024
auto-merge was automatically disabled
December 3, 2024 12:01
Pull request was closed
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.
The Trivy Docker image scanner workflow sometimes fails because of rate limiting. If we can cache the database for 24hrs it might relieve some of those issues.