Open marcincuber opened 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Hey @marcincuber 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you supply a sample Terraform configuration that exhibits this behavior?
@justinretzolk I updated the issue with sample configuration.
Any news on this issue? I have the same problem and it makes it really hard to work with the transitgateway together with directconnect.
@marcincuber - did you find any solution on this?
this is a critical feature and the downtime created by Terraform is unacceptable...
@justinretzolk May I know if there is any update to this issue? This creates service interruption to all DX associations when we add new prefixes...
Terraform Core Version
1.4.1
AWS Provider Version
4.58
Affected Resource(s)
Expected Behavior
When updating
aws_dx_gateway_association
with an additionalallowed_prefix
. Gateway association should be updated in-place with zero impact on other prefixes.Actual Behavior
Update to
aws_dx_gateway_association
resource causesaws_ec2_transit_gateway_route_table_association
replacement which is disabling all the traffic through the dx gateway.Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Plan Output
Steps to Reproduce
Implement
aws_dx_gateway_association
which is associated with transit gatewayaws_ec2_transit_gateway_route_table_association.dx_gateway
Important Factoids
aws_ec2_transit_gateway_route_table_association.dx_gateway_lnd_eng_1
must be replaced action shouldn't be happening as allowed prefixes can be updated in place.References
Related docs -> https://docs.aws.amazon.com/directconnect/latest/UserGuide/allowed-to-prefixes.html
Would you like to implement a fix?
None