IT-3421: Add vulnerability scanning to repo #6
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
…lts, and stop if Trivy fails
…docker using 'type=docker'
zaro0508
requested changes
Jul 26, 2024
zaro0508
approved these changes
Jul 29, 2024
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.
This PR adds vulnerability scanning to the repo' using Trivy.
The workflow to build and publish a container will fail if there are HIGH or CRITICAL findings.
There is also a daily scan to see if there are new, major vulnerabilities for already published containers.
When a container image IS published, in addition to being published to the tag major.minor.patch,
it is published to the tag major.minor. This allows us to make security updates to existing containers.