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 false failures with trivy config scan #1652

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

tkatila
Copy link
Contributor

@tkatila tkatila commented Jan 17, 2024

No description provided.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d169cb8) 51.94% compared to head (c63da6a) 51.94%.

❗ Current head c63da6a differs from pull request most recent head cb5229f. Consider uploading reports for the commit cb5229f to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1652   +/-   ##
=======================================
  Coverage   51.94%   51.94%           
=======================================
  Files          42       42           
  Lines        4911     4911           
=======================================
  Hits         2551     2551           
  Misses       2210     2210           
  Partials      150      150           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@tkatila tkatila force-pushed the trivy-config-false-failures branch 2 times, most recently from f43d0a5 to f477724 Compare January 17, 2024 09:58
Sadly GH's trivy-action doesn't support the trivyignore.yaml file.
The whole detection class needs to be ignored.

Include the .yaml file for future use.

Signed-off-by: Tuomas Katila <[email protected]>
@tkatila tkatila force-pushed the trivy-config-false-failures branch from f477724 to 7e8aba1 Compare January 17, 2024 10:17
@mythi mythi merged commit 4059067 into intel:main Jan 18, 2024
77 checks passed
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