Open mmoreno43 opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @mmoreno43 š Thank you for taking the time to raise this! So that we have the appropriate information in order to look into this, can you supply debug logs (redacted as needed) as well?
Terraform Core Version
1.3.7
AWS Provider Version
5.8.0
Affected Resource(s)
I have some terraform code that is supposed to add propagations to my ec2 transit gateway route table. Each time I run my terraform, the code is re-ran when no changes have been made. I believe the affected resources are:
Expected Behavior
What I expect to happen is the code to look up the ID based on the name in data sources and retrieve the ID. The ID is then used to propagate the correct attachment to my transit gateway route table.
Actual Behavior
What ends up happening is the data sources look up the name of the attachment and fetch the new ID. Terraform destroys the old propagation and creates a new one.
Now, you may be asking yourself why not use a lifecycle configuration, if I used a lifecycle rule and someone re-created a VPC attachment then the new attachment will never get associated.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
tgw.txt
###################### Main Module ######################
####################### Variables #######################
########################## Child Module #########################
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None