IT-3921: Rebuild container when Trivy code scan fails #7
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.
This repo' runs a daily scan of the built container image using Trivy and reports its findings to on the repo's Security tab. When findings appear they can almost always be addressed simply by rebuilding the image, which picks up updates to the dependencies. In this way rebuilding the Docker image is analogous to patching a linux server.
This PR adds logic to the daily scan to automatically trigger a rebuild of the image when the scan fails, by incrementing the semvar tag. If the rebuild is successful an updated image will be pushed to ghcr.io. If the rebuild fails to address the findings then no new image will be pushed, and instead the IT team will see the findings in the Security tab, and investigate, following our current process.