aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[Resource Type] - [Enhancement] - Add new automatically generated "aws:cloudformation:*" tags to each Stack created by a StackSet.
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::CloudFormation::StackSet
### Resource name
_No response_
### Description
Please add new automatically generated "aws:cloudformation:*" tags to each Stack created by a StackSet so that the Stack tags point back to the StackSet that created. the Stack. This is just like the automatically generated tags that Stacks apply to resources they create, namely the Resource Tags (https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-resource-tags.html).
Such reverse pointers in tags have proven extremely useful in supressing making direct changes to dependent resources by pointing back to the creating Stack and thus avoiding Stack drift. This issue requests the same for StackSets. It's even more useful for StackSets because the dependent Stacks created by a StackSet can and likely are in a different AWS Region, a different AWS Account, or both, making the StackSet incredibly hard to find from a resource walking backwards thru it's creating Stack. I'd suggest this is even more helpful than the forward pointers in the Stack Instances of a StackSet, at least for, avoiding Stack and StackSet drift.
Minimally sufficient new tags:
1. Key=aws:cloudformation:stack-set-id Value=
Additional Tags that would be helpful, but not completely necessary because the values are already encoded in the Stack Set ARN could be:
1. Key=aws:cloudformation:stack-set-name Value=
2. Key=aws:cloudformation:stack-set-region Value=
3. Key=aws:cloudformation:stack-set-account Value=
### Other Details
_No response_
Contributor guide
Research direction
Start with the AWS::CloudFormation::StackSet resource and the linked AWS CloudFormation Resource Tags documentation. Determine how tags are propagated to each Stack created across accounts and Regions, then verify that the requested aws:cloudformation:stack-set-id tag is present and that the optional name, Region, and account tags follow the proposed values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100