ci: add trivy container vulnerability scanning pre-merge#399
Open
jay7-tech wants to merge 1 commit intodrasi-project:mainfrom
Open
ci: add trivy container vulnerability scanning pre-merge#399jay7-tech wants to merge 1 commit intodrasi-project:mainfrom
jay7-tech wants to merge 1 commit intodrasi-project:mainfrom
Conversation
Signed-off-by: jay7tech <jayadeepgowda24@gmail.com>
jay7-tech
force-pushed
the
feature/gsoc-trivy-scan
branch
from
69881c1 to
7b1cbe3
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
The
build-testworkflow currently builds 30+ microservices for E2E testing without running a dedicated container vulnerability scan. High/Critical CVEs inherited from base images could merge undetected.This PR adds local
aquasecurity/trivy-actionscanning directly within thebuild-imagesmatrix. It scans the generated.tarartifacts forCRITICALorHIGHvulnerabilities across all variants and fails the action if any are found (where a fix is available).Scanning the local tarball avoids registry push overhead, securing the build phase with negligible latency cost.
Type of change
Fixes: N/A (Infrastructure Proactive Patch)