Incorrect terraform submodules scanning #7106
Closed
ajax-ryzhyi-r
started this conversation in
Bugs
Replies: 1 comment
-
Hi @ajax-ryzhyi-r ! Thanks for the report. Track #7113 |
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
-
Description
When there is a submodule call in terraform configuration trivy scans the parent module instead of the submodule. For example, when I have karpenter module call in configuration (
terraform-aws-modules/eks/aws//modules/karpenter
):trivy scans parent eks module instead
terraform-aws-modules/eks/aws
:This issue appeared in the 0.53.0 version everything was ok in 0.52.2
Desired Behavior
Trivy scans submodules code instead of parent module
Actual Behavior
Trivy scans parent module code instead of submodule
Reproduction Steps
1. Create root terraform module with `terraform-aws-modules/eks/aws//modules/karpenter` public module call 2. Run trivy scan
Target
AWS
Scanner
Misconfiguration
Output Format
Table
Mode
Standalone
Debug Output
Operating System
macOS Sonoma
Version
Checklist
trivy clean --all
Beta Was this translation helpful? Give feedback.
All reactions