Cloudformation-coverage-roadmap: AWS::ElasticBeanstalk::Environment should allow tags to be updated

[rshayman]

Although ElasticBeanstalk fully supports tags allows them to be updated, CloudFormation still does not allow this. Attempting to do so results in the error

Elastic Beanstalk environment tags cannot be updated.

Not being able to update the tags associated with a Beanstalk instance is a real pain operationally.

[aleung241]

We're having issues with this too.
Adding/updating tags works fine through the console and CLI, there's no reason why this shouldn't work with CloudFormation templates.
From our what we can see, it just updates the backing CloudFormation template TAGS for the Elastic Beanstalk without changing any of the other resources.

[CaptainJojo]

Same here

[rshayman]

I thought coming soon means the feature would ship in a few weeks. It has been now been in this state for nearly 4 months!!!

[bhechinger]

Not to mention the fact that Elastic Beanstalk gained the ability to change tags in the middle of 2016!

[Blaze34]

any updates?

[daysofwineandroses]

Any progress on releasing this?

[Throckmortra]

please release :)

[rshayman]

I would like to know what your definition of coming soon is. It certainly isn't what's advertised

Coming soon - nearing completion, likely being planned for an upcoming coverage update release. Think a couple of weeks out, give or take.

[oesah]

Ok, so this is really annoying. I am stuck with cloudformation at step UPDATE_FAILED | Elastic Beanstalk environment tags cannot be updated. I cannot see which tags it tries to change so I can put it back to the current one. And I thought all these cloud tools should make life easier, but the more I work with cloudformation, the more frustrated I get...

[benbridts]

@oesah

• If there was nothing else that updated the tags, the current CloudFormation template should still contain the original tags
• If there was, you can still look in the ElasticBeanstalk console to see what the tags are right now.
• In the second case, you could use the API to bring ElasticBeanstalk back in sync with CloudFormation

Changing the tags to the values you want after that can still be tricky. I usually prefer replacing the complete ElasticBeanstalk environment (using a blue-green / 2 step deployment), but that can be tricky if you have state in the environment.

[benbridts]

This seems to be fixed!

Tags
Specifies the tags applied to resources in the environment.
Required: No
Type: List of Tag
Update requires: No interruption

link

[nelsonjchen]

@benbridts

https://github.com/awsdocs/aws-cloudformation-user-guide/blame/31146631d5dc7a04d5f0bd58c8abeec6e1118f5a/doc_source/aws-properties-beanstalk-environment.md#L123

That entry in the documentation hasn't changed for two years.

[benbridts]

@nelsonjchen My coworker tested it, and it seems to work as documented now

[rohits-spec]

This is shipped and available in all regions.

[Throckmortra]

Tested this today. So now it doesn't throw a cloudformation error but it doesn't seem to actually update the tags despite the new tags being present in cloudformation