cloudformation-coverage-roadmap
cloudformation-coverage-roadmap copied to clipboard
aws-cloudformation
AWS::Events::Rule - Tags
1. Title
AWS::Events::Rule-Tags
2. Scope of request
A new attribute for an existing resource is desired
3. Expected behavior
In Create and Update, it should include tags, like the console.
4. Suggest specific test cases
Tags should be supported in CloudFormation for all resources that support tags
5. Helpful Links to speed up research and evaluation
API Doc: https://docs.aws.amazon.com/eventbridge/latest/APIReference/API_PutRule.html
6. Category (required) - Will help with tagging and be easier to find by other users to +1
- Integration (MQ, SQS, SNS,...)
7. Any additional context (optional)
Is there any update on this? We're trying to use the Scheduled Event timezone adjuster to ensure our rules fire based on local time, but until this is supported we're having to apply the tags with the CLI post deployment.
Just as an aside, it's still so frustrating to find these gaps in Cloudformation. It makes it so hard to create comprehensive, reliable deployments. Given this is AWS's infrastructure as code tool, that's not great.
@craigsands
If you react with the 👍 button to the original issue, (the first comment, click on the smiley face if you're the first reacting), your votes can be used to sort issues and determine priorities.
A comment will send a notification to everyone (participants and watchers), but cannot be easily counted as a vote for an issue. Thus It's generally better to vote than to comment with "+1". To keep up to date, you can also add yourself as a watcher.
There have been some good improvements to CF over the years but the lack of attention on this missing feature sucks something fierce. It's an extra burden for those of us running IaC apps, especially with EventBridge and lots of systems using the bus or lots of micro-services and other resource-heavy systems. Please add tagging support so I can (easily) accurately track and try to predict monthly costs or give us a different way to do cost analysis without creating a bunch of resources just to tag resources.
So here I am, not only staring down the barrel of another daylight savings change and having to check all our rules are tagged, but also getting leant on to provide better cost allocation. I note that three of the top most +1'd issues in this repository are about tagging. I get that it's not the most critical functionality, but so much of AWS relies on consistent and comprehensive tagging. These gaps are such annoying frustrations in Cloudformation: not show stoppers, but they have such widespread impact.
@benkehoe over 200 hundreds of the +1 - is there a chance that this would be closed?
Why this takes soooo long? Any updates or is there any specific date this will be released?
Still in Researching after more than 2 years!!!
Excuse my pedantry @vumdao, but it's actually over 3 years :disappointed: We are also having to support a manual workaround for this. Even Terraform can do it, why not CloudFormation?
Would be a great time to implement this as even AWS Config now supports AWS::Events::Rule
Is there any update on that? As it's not currently available it prevent our teams from complying with tagging strategy while using cloud-formation.
How is the research progressing? Would solve a lot of headaches if this issue was resolved.
We rely on tags to track costs and more. Please, could be possible to support tags on rules?
Thank you for your patience on this issue. We've brought this feedback to the relevant team, and they'll be working on an update in the upcoming months.
Thank you for your patience on this issue. We've brought this feedback to the relevant team, and they'll be working on an update in the upcoming months.
Thank you so much!