[BUG] Is there anyway to handle terraform resources in nested child_modules ?

[Shinyaigeek]

Kind of proposals

• Parser
• Linter
• Simulator
• Testing
• Terraform

Describe the problem

Currently, I am working to set up Fastly Deliver service with Terraform. My terraform project's directory structure is like below:

- terraform/
  - modules/: Define fastly service needed in my project as Terraform module. 
    - app/: accumulate fastly resources defined in `common/` as a single fastly service
    - common/: Define fastly resources
  - env/: Pass variables to fastly service defined in `modules/` according to it's environment
    - dev/
    - prod/

In the above directory structure, falco does not display any result in terraform -chdir terraform/env/${env} show -json planned.out | falco -vv terraform lint.

In my understanding, terraform will generate fastly resources in planned_values.root_module.child_modules.child_modules.resources on the output json by command terraform -chdir terraform/env/${env} show -json planned.out with the above terraform structure because of the module dependency env -> app -> common. In other word, fastly resources will be generated in nested child_modules.

falco/terraform/terraform.go

Line 154 in 0eebb52

for _, v := range root.PlannedValues.RootModule.ChildModules {

Currently, falco seems not to be able to handle nested child_resources as the code implies.

Is this behavior a bug? or Is there anyway to handle nested child_modules?

VCL code that cause the problem / reproduceable

- terraform/
  - modules/
    - app/
    - common/
  - env/
    - dev/
    - prod/

I can create the reproduction repository or provide with the json generated by terraform show -json if you want.

Expected behavior

falco can handle nested child_modules

Desktop (please complete the following information)

required

• OS: M1 Mac
• Shell: bash