Infrastructure teams duplicate tags across IaC resources
Terraform and Terragrunt users want consistent default tags without repeating tag definitions in resources or child configurations. A related AWS CDK request highlights a gap in propagating tags to associated resources such as log groups. The requests show friction across IaC tools, but a standalone tool could audit and reduce inconsistencies; it cannot add provider-native behavior where the platform lacks it.
For infrastructure engineers using Terraform, Terragrunt, and AWS CDK. Mentioned from Jun 2022 to May 2023 on GitHub.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 4.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
It would be great if it were possible to define a set of default tags at the provider level, that automatically get applied to all resources managed by a given provider instance
having this will save us from duplicating a lot of tags in resources or locals/variables
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks