Closed Sinnohd closed 3 years ago
Hi @bflad
This looks like a bug that has been around for quite some time. @nijave has created a seemingly trivial patch for this in https://github.com/terraform-providers/terraform-provider-aws/pull/14380. Would you be willing to look at this?
Thanks, Boris
Hi @Sinnohd! It looks like this has been fixed on the AWS side. I'm going to be merging a test today that checks for this.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!
Community Note
Terraform Version
terragrunt version v0.19.11 Terraform v0.12.5 provider.aws v2.21.1
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
It should create the defined associations and store them in the state file.
Actual Behavior
It creates the correct associations in AWS, but stores in the state file three times the association with one of networks!
Except from state file, same "subnet_id" for every entry, where it should be subnet-network1 to subnet-network3:
If you do the apply from step three below, it triggers additional bugs with wait states not handled correct.
Steps to Reproduce
terraform apply
terraform plan
Important Factoids
References