-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws_ec2_transit_gateway_vpc_attachment does not set transit_gateway_default_route_table_association or transit_gateway_default_route_table_propagation correctly #8383
Comments
I have basically a "me-too" here, but on 0.12-beta2
and I'm sure it was the same with this combo
|
We are having this issue as well. One thing to note, attachments for VPCs in the same account as the transit gateway do not exhibit this behavior. This only occurs with attachments that are created in another account using RAM. |
@BrandonsAccount @piersf @jeffmccollum @furtber
but I agree we should do something to try and stop this drift being detected in case the attributes are set mistakenly, especially since a second
For cross-account VPC attachments maybe the correct resource to specify the default route table attributes on is the vpc_attachment_accepter resource? See #8679 (comment). |
This is my Transit Gateway:
As you see Then my VPC attachment initially was this:
But, by using the above I run into this issue.
To "escape" from this drift issue I set it to So in the end, either I have the issue here #8383 when using So in the end what I have done was this:
This detects if the account is the same or not as the TGW and sets the values to "escape" both issues. But what I really need is this drift issue to be fixed so I can come back to set |
Any chance we can fix this annoying problem? |
Another solution as workaround:
|
Has there been a fix for this? The issue is still present in The same issue is mentioned in #8600 Thank you! |
issue is still present, i am using |
The issue is really annoying. It happens on cross-account VPC attachment. |
Relates #8383. |
me too. I have the same issue. This issue exists from 3 years. No fix until now :( |
Based on testing, this appears to have been resolved. If you're still encountering this issue, please open a new issue. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
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. |
Community Note
Terraform Version
Issue reproduced on 11.11 and 11.13.
I can confirm that this was not a bug in aws provider version 2.0.0. The issue exists in version 2.7.0.
Affected Resource(s)
Terraform Configuration Files
This is the plan output
Expected Behavior
Running
terraform state show aws_ec2_transit_gateway_vpc_attachment.this
should show this...It also should not detect drift immediately after applying these changes.
Actual Behavior
Running
terraform state show aws_ec2_transit_gateway_vpc_attachment.this
shows this...When running
terraform apply
a second time, the following drift is reported (but the apply runs successfully). It looks like this...The terraform state shows the correct values after the 2nd apply...
Every
terraform apply
moving forward continues to detect drift though...Steps to Reproduce
There's a fair amount of setup involved so I don't know that I can cover it all...
Important Factoids
The text was updated successfully, but these errors were encountered: