search

aws-solutions / network-orchestration-for-aws-transit-gateway

The Network Orchestration for AWS Transit Gateway solution automates the process of setting up and managing transit networks in distributed AWS environments. It creates a web interface to help control, audit, and approve (transit) network changes.
https://aws.amazon.com/solutions/implementations/serverless-transit-network-orchestrator/
Apache License 2.0
113 stars 48 forks source link

Updated tags in v2.0.0 causes replacement of Transit Gateway and its route tables #17

Closed david-prado closed 1 year ago

david-prado commented 3 years ago

Upgrading STNO from v1.0.0 to v2.0.0 causes a replacement of Transit Gateway and its route tables due to changes in the tags, as documented here

This also caused duplicate Transit Gateway and Route tables due to the Retain policy.

groverlalit commented 3 years ago

@david-prado Thanks for bringing this to our attention. We have not seen this behavior in our testing. It would be great if you could open a support case via the console to allow us to obtain and review the logs. Thanks.

david-prado commented 3 years ago

I have opened a support case with instructions to contact you so you can look at the logs. Thanks

maykays commented 3 years ago

@david-prado Was your issue resolved?

kbosco commented 3 years ago

I am facing a similar issue in our customer environment which is preventing us from promoting v2.0.0 to production. Anyone found a workaround for this? @david-prado

david-prado commented 3 years ago

I am facing a similar issue in our customer environment which is preventing us from promoting v2.0.0 to production. Anyone found a workaround for this? @david-prado

We just updated the v2.0.0 template with same tags as previous version. That prevents the replacement

groverlalit commented 1 year ago

This issue has been resolved. CFN now supports name replacement as an update without interruption.