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'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Mar 29, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugcorev0.12Issues (primarily bugs) reported against v0.12 releases
Terraform Version
Terraform Configuration Files
main.tf
./modules/mod1/main.tf
Debug Output
Crash Output
Expected Behavior
When the modules are removed from the terrafrom file they should be deleted in the correct order. First modB then modA
Actual Behavior
When the modules are removed from the terrafrom file they are destoryed in a random order
Steps to Reproduce
create main.tf whith modA and modB
terrafrom apply
remove modA and modB from main.tf
terraform apply
do this a couple of times. The destroy order is random sometimes first modB sometimes first modA
Additional Context
When doing "terraform destroy" the depencies are taken into account
References
The text was updated successfully, but these errors were encountered: