You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there needs to be functionality in highlander core to manage tagging on an individual resource level through configuration.
My example is say the ecs template has a Name tag of Name: ${Environment}-ecs-xx but i want that to be Name: ${Environment}-${cluster}-ecs-xx. We could build that functionality into the template but i feel it would be something we'd repeat in a lot of templates.
Some example config for setting tags
Tags:
Project: myApp # Tag is added to all resources that can have tagsEcsAsg: # Resource NameName:
Sub: ${Environment}-${Cluster}-ecs-xx
Also the ability to set global tags across all resources that could contain tags would be a good thing to have as well. However that maybe a difficult task as not all cloudformation resources use the Tag property to declare tags
The text was updated successfully, but these errors were encountered:
@Guslington in it's simplest form it is possible to read resource definition file downloaded by cfndsl and check wether resource being rendered supports Tag property.
I think there needs to be functionality in highlander core to manage tagging on an individual resource level through configuration.
My example is say the ecs template has a Name tag of
Name: ${Environment}-ecs-xx
but i want that to beName: ${Environment}-${cluster}-ecs-xx
. We could build that functionality into the template but i feel it would be something we'd repeat in a lot of templates.Some example config for setting tags
Also the ability to set global tags across all resources that could contain tags would be a good thing to have as well. However that maybe a difficult task as not all cloudformation resources use the
Tag
property to declare tagsThe text was updated successfully, but these errors were encountered: