aws-cloudformation / cloudformation-coverage-roadmap

The AWS CloudFormation Public Coverage Roadmap
https://aws.amazon.com/cloudformation/
Creative Commons Attribution Share Alike 4.0 International
1.11k stars 56 forks source link

AWS::EC2::TransitGateway* #354

Open ckabalan opened 4 years ago

ckabalan commented 4 years ago

1. Title

All resources and properties matching AWS::EC2::TransitGateway*.

2. Scope of request

All properties are marked to require replacement in CloudFormation, however many properties can be updated via the API without replacement. Most notably the "Tags" property.

Example AWS::EC2::TransitGateway-Tags say "Update requires: Replacement", however via the AWS Console you can update tags without replacement.

Most properties I think can be updated manually (API / Console) but none of them are able to be updated via CloudFormation.

3. Expected behavior

CloudFormation has accurate support for the update-ability of TransitGateway-related resource proprties. "Tags" and other applicable properties should be able to be updated without the re-creation of a new resource.

4. Suggest specific test cases

N/A

5. Helpful Links to speed up research and evaluation

N/A

6. Category (required) - Will help with tagging and be easier to find by other users to +1

Networking & Content (VPC, Route53, API GW,...)

7. Any additional context (optional)

N/A

Oatelaus commented 1 year ago

This makes managing this infrastructure in IaC really difficult

The linked issue #531 has been done already which fixed TransitGateway in 2021 - is it possible to address these too?

reaperharvest commented 10 months ago

We just had an outage because of this unexpected behavior. Yes the docs clearly display on the cloudformation resource page that an update to tags would cause a replacement, but who would realistically look at every cloudformation resource doc when you are just trying to tag your resources for cost tracking purposes? Tagging should absolutely not be causing replacement of resources. Shame on AWS for not even responding/assigning this request. I'll probably open another just to see if we can get traction.