Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

In-line issue suppression within Infrastructure as Code material #3900

Closed
huornlmj opened this issue Mar 24, 2023 · 4 comments
Closed

In-line issue suppression within Infrastructure as Code material #3900

huornlmj opened this issue Mar 24, 2023 · 4 comments
Labels
triage/support Indicates an issue that is a support question.
Milestone

Comments

@huornlmj
Copy link

huornlmj commented Mar 24, 2023

As a user I would like to be able to place checker suppression within my IaC code so that I can selectively accept issues. Most security tools allow for a number of suppression methods, e.g. exclude a file, disable a checker by ID, and finally put an inline comment with something like #nosec to skip the line. Trivy doesn't appear to have this. In fact it only seems to allow for complete file exclusion which is too far the other direction.

@huornlmj huornlmj added the triage/support Indicates an issue that is a support question. label Mar 24, 2023
@huornlmj huornlmj changed the title In-line issue suppression In-line issue suppression within Infrastructure as Code material Mar 24, 2023
@knqyf263
Copy link
Collaborator

#trivy:ignore: should work. Are you talking about something else?
#2961

@itaysk
Copy link
Contributor

itaysk commented Mar 27, 2023

BTW which language you need it for?

@huornlmj
Copy link
Author

@itaysk K8s YAML object files, but pretty any IaC material Trivy covers.

@creste
Copy link

creste commented Apr 5, 2023

I also need #trivy:ignore:... to work with IaC, specifically k8s yaml files used as templates in helm charts.

@itaysk itaysk added this to the v0.41.0 milestone Apr 10, 2023
@itaysk itaysk mentioned this issue Apr 11, 2023
@knqyf263 knqyf263 modified the milestones: v0.41.0, v0.42.0 May 3, 2023
@aquasecurity aquasecurity locked and limited conversation to collaborators May 10, 2023
@knqyf263 knqyf263 converted this issue into discussion #4293 May 10, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
triage/support Indicates an issue that is a support question.
Projects
None yet
Development

No branches or pull requests

4 participants