Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: omitted severity flags in docker image scan action #142

Merged
merged 3 commits into from
Aug 22, 2024

Conversation

pankajmouriyakong
Copy link
Contributor

@pankajmouriyakong pankajmouriyakong commented Aug 21, 2024

  • Update to Step "Generate docker-cis JSON report", removed severity flag as it was causing warnings "unknown severity option: unknown severity: FALSE"
  • Update to Step "Inspect docker-cis report", removed severity flag as it was causing warnings "unknown severity option: unknown severity: FALSE"
  • This severity flag is not being used at this point. Trivy uses this flag to restrict the scan to specific severity levels
  • Because of no explicit severity flag, shared action uses value of global_enforce_build_failure env defined in our scripts

@pankajmouriyakong pankajmouriyakong requested review from a team as code owners August 21, 2024 13:10
@CLAassistant
Copy link

CLAassistant commented Aug 21, 2024

CLA assistant check
All committers have signed the CLA.

Copy link

github-actions bot commented Aug 21, 2024

Luacheck Report

1 files  ±0  1 suites  ±0   0s ⏱️ ±0s
4 tests ±0  4 ✅ ±0  0 💤 ±0  0 ❌ ±0 
8 runs  ±0  8 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 56a8bc2. ± Comparison against base commit 5c685ec.

♻️ This comment has been updated with latest results.

@saisatishkarra
Copy link
Collaborator

@pankajmouriyakong pls sign-off the commits as CLA requirement and follow comment

- Update to Step "Generate docker-cis JSON report", removed as it was causing warnings "unknown severity option: unknown severity: FALSE"
- Update to Step "Inspect docker-cis report", removed severity env as it was causing warnings "unknown severity option: unknown severity: FALSE"
- This severity flag is not being used at this point. Trivy uses this flag to restrict the scan to specific severity levels
- Because of no explicit severity flag, shared action uses value of global_enforce_build_failure env defined in our scripts
@saisatishkarra saisatishkarra merged commit f19e9a7 into main Aug 22, 2024
12 checks passed
@saisatishkarra saisatishkarra deleted the SEC-1173-update-trivy-flags branch August 22, 2024 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants