Closed mattwilder closed 6 months ago
Voting for Prioritization
Volunteering to Work on This Issue
This functionality has been released in v5.41.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.
For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!
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.
Description
Similarly to the issue presented in #26754, it is impossible to fully automate the use of
aws_ec2_transit_gateway_prefix_list_reference
with peering attachments because there is no way to tell if the peering attachment has been accepted or not. If theaws_ec2_transit_gateway_peering_attachment
data source were to include the attachment state, then one could prevent the creation of the prefix list reference until the attachment state is available.Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
This would solve the same problem reported in #26754 in another way
Would you like to implement a fix?
None