-
Notifications
You must be signed in to change notification settings - Fork 298
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
bug(ansible): not detecting yaml inventory since v1.7.11 #6814
Comments
Hi @timo-fc , Thank you for your input! |
Hello @gabriel-cx sorry for the log delayed response. Even the official documentation isn't mentioning it: This file is detected and scanned in 1.7.12
but the corresponding host_vars/webserver1.yml and group_vars/subgroup.yml are not scanned an inventory file without all: is not scanned
In Version 1.7.10 everything works as expected. All inventory files and the corresponding group_vars and host_vars files are checked. |
Hi @timo-fc , Thanks for your input! |
Thanks v1.7.13 has fixed it for me. |
Since Version 1.7.11 the yaml inventory files are not detected anymore and therefor not scanned.
Expected Behavior
With v1.7.10 I get the expanded behavior
docker run -t -v /path/to/inventory:/path checkmarx/kics:v1.7.10 scan -p /path
`Scanning with Keeping Infrastructure as Code Secure v1.7.10
Preparing Scan Assets: Done
Executing queries: [---------------------------------------------------] 100.00%
Files scanned: 332
Parsed files: 329
Queries loaded: 292
Queries failed to execute: 0`
and e.g., secrets in them are correct detected
Actual Behavior
With v1.7.11 no files are detected
docker run -t -v /path/to/inventory:/path checkmarx/kics:latest scan -p /path
`Scanning with Keeping Infrastructure as Code Secure v1.7.11
Files scanned: 0
Parsed files: 0
Queries loaded: 0
Queries failed to execute: 0`
Steps to Reproduce the Problem
The inventory folder contains multiple yaml files with hosts:
group1.yml
and sub folders group_vars and host_vars with yaml files for vars
group_vars/sub_group.yml
Specifications
The text was updated successfully, but these errors were encountered: