You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running terragrunt init for four modules. The first two modules execute successfully, and their respective state.tf files contain the expected resources and outputs.
However, the third module, which depends on the first and second modules, ends up with an empty state.tf (no resources, no outputs), even though there are many resources that should be created. However, this causes an error when creating the fourth module, and later during terragrunt plan and apply...
Why does the third module's state.tf remain empty after init, even though the resources are displayed in the plan and apply logs?
Steps To Reproduce
terragrunt run -all init
Expected behavior
The state file for the third module contains all resources and defined outputs, so the fourth module initializes successfully, and terragrunt plan and apply execute successfully
Versions
terraform version: 1.5.3
ashicorp/azurerm : v3.90.0
Additional context
Logs error:
Debug Output
18418Z Initializing the backend...
18623Z
19177Z Initializing provider plugins...
19938Z - Reusing previous version of hashicorp/azurerm from the dependency lock file
20808Z - Reusing previous version of hashicorp/random from the dependency lock file
21628Z - Using previously-installed hashicorp/azurerm v3.90.0
22535Z - Using previously-installed hashicorp/random v3.4.3
23008Z
23720Z Terraform has been successfully initialized!
24391Z
24877Z You may now begin working with Terraform. Try running "terraform plan" to see
25733Z any changes that are required for your infrastructure. All Terraform commands
26260Z should now work.
26436Z
26893Z If you ever set or change modules or backend configuration for Terraform,
27594Z rerun this command to reinitialize your working directory. If you forget, other
28660Z commands will detect it and remind you to do so if necessary.
28948Z
29733Z time=Z level=error msg=1 error occurred:
31176Z * /azp/_work/r1/a/_IaC-AzureKubernetesService/drop/s/environments/dev/azureKubernetesServiceNamespace/terragrunt.hcl:43,78-87: Unsupported attribute; This object does not have an attribute named "aks_name".
31839Z
31985Z
33026Z time=Z level=error msg=Unable to determine underlying exit code, so Terragrunt will exit with error code 1
65011Z ##[error]Script failed with exit code: 1
73998Z [command]/usr/bin/az account clear
Describe the bug
I am running terragrunt init for four modules. The first two modules execute successfully, and their respective state.tf files contain the expected resources and outputs.
However, the third module, which depends on the first and second modules, ends up with an empty state.tf (no resources, no outputs), even though there are many resources that should be created. However, this causes an error when creating the fourth module, and later during terragrunt plan and apply...
Why does the third module's state.tf remain empty after init, even though the resources are displayed in the plan and apply logs?
Steps To Reproduce
terragrunt run -all init
Expected behavior
The state file for the third module contains all resources and defined outputs, so the fourth module initializes successfully, and terragrunt plan and apply execute successfully
Versions
Additional context
Logs error:
The module's state file :
terragrunt.hcl for this module:
The text was updated successfully, but these errors were encountered: