Closed Eagleman7 closed 6 months ago
Thank you for opening this issue! Can you confirm that pinning to 4.3.1 still works?
Hey @drewmullen,
4.3.1 works fine for me. I hardcoded all the VPC modules we use to version 4.3.1.
So it looks like the error is originating from this commit: https://github.com/aws-ia/terraform-aws-vpc/commit/8de0920f9ba7f8774b2fee96f41bccecf0c23225
As a quick n dirty test can you please try adding a tag to your tgw subnets? Formatting might be off below... typing from my phone 😅
subnets = {
private = {
netmask = 26
}
transit_gateway = {
netmask = 28
transit_gateway_default_route_table_association = true
transit_gateway_default_route_table_propagation = true
transit_gateway_appliance_mode_support = "disable"
transit_gateway_dns_support = "disable"
tags = {
subnet_type = "tgw"
}
}
}
I believe the bug is on our end (which seems obvious but worth acknowledgeling). When we added this subnet tag reference we did not add in the try()
safety guard
And the problem becomes pretty clear.
We'll get this fixed but I think as a temp workaround you can specify a tag that will propagate to the attachment
Thanks for the work-around and fixing the issue!
It seems I didnt tag everything yet as well for the VPC's becaused I missed the tags block in the TGW section :)
I'm trying to upgrade from 4.3.1 to 4.3.2. When doing a plan I get the following error:
I'm using the following TF code in the plan: