Replies: 2 comments 1 reply
-
|
Thanks for the detailed report, we will look through it and get back to you. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi @cawolf ! Track #6603 |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you very much for the prompt fix! We ran it today and it worked like a charm with an existing Terraform cache. 🎉 |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
When using trivy for our terraform configuration, we ran into an issue regarding the local terraform cache located in
.terraform. Trivy 0.50.2 seems to ignore the local cache completely, and instead tries to fetch the modules remotely. In our special case, this leads to a subsequent error (we are using the GitLab terraform registry, which is currently not supported by trivy), which makes trivy not runnable for us.After some debugging, we found that the filesystem used to open the
.terraform/modules/modules.jsonfile is filtered down to terraform files only (".tf", ".tf.json", ".tfvars"), and thus is not able to open the modules.json file ever. Naively fixing the filepkg/iac/detection/detect.go:247to also contain the modules.json file fixes the problem locally for us.Desired Behavior
The terraform cache in
.terraformshould be used.Actual Behavior
The terraform cache in
.terraformis ignored, the debug log outputs:Reproduction Steps
terraform versionterraform inittrivy config .Operating System
Ubuntu 22.04.4 LTS
Version
Checklist
trivy image --resetBeta Was this translation helpful? Give feedback.
All reactions