Replies: 2 comments
-
|
Seems like a reasonable ask, wdyt @nikpivkin? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Track #9911 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
helm misconfiguration scan ignores the files with
ymlextension intemplatesdirectoryDesired Behavior
helm misconfiguration should also scan the files with
ymlextension intemplatesdirectoryi think that the bug/solution might be here:
please also note that the
matchers[FileTypeHelm]is overridden - first defined here, then redefined hereActual Behavior
helm misconfiguration scan skips the files with
ymlextension intemplatesdirectoryReproduction Steps
using trivy's testsdata test chart:
scan correctly detects all
*.yamlfiles that are used (deployment.yaml, service.yaml, and serviceaccount.yaml):if we change the extension of eg, deployment and serviceaccount to
yml, those files will be ignored - ie, scan will incorrectly skip all '*.yml' files that are required (deployment.yml and serviceaccount.yml in this example) and only detect service.yaml:Target
Filesystem
Scanner
Misconfiguration
Output Format
Table
Mode
Standalone
Debug Output
before
yamltoymlfile extension change:after
yamltoymlfile extension change:Operating System
openSUSE Tumbleweed
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions