aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
Applying tags to CloudFormation resources during the CodeDeploy deployment step CodePipeline
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
Other
### Resource name
CodePipeline Resource tagging
### Description
When creating a stack with the CloudFormation console, it is possible to provide tags that you would like to be attached to all resources provisioned. When creating a stack from a template file from source artifact with CodePipeline, there is no option to create tags that will be applied to all launched resources. This a request to add this feature to CodePipelines functionality.
### Other Details
We have automated the deletion of resources that do not include certain tags, currently these tags must be present in our CloudFormation template. There is no way to tell CloudFormation from CodePipeline to add a uniform tag for each resource launched from the template.
Contributor guide
Research direction
No repository files, tests, or implementation entry points are named. Start by reviewing the CloudFormation console tagging behavior and the CodePipeline flow that deploys a template from a source artifact, including the CodeDeploy deployment step. Done means defining and implementing a supported way for uniform tags to reach all resources provisioned through that flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100