Both sam deploy and aws cloudformation deploy CLI commands support an optional --tags argument. This tags argument is the preferred way to apply resource tags across all resources in the CloudFormation stack. Since SAM CLI is not a first-class citizen for Spacelift, the samconfig.toml file cannot be used to customize tags either since the tags in samconfig.toml are only evaluated when a sam deploy occurs.
Similar to the special TF_VAR_ variables supported by Spacelift, I would like to see a CF_VAR_STACK_TAGS (CloudFormation variable) or similar that would be automatically passed to the aws cloudformation deploy command that is executed behind the scenes for CloudFormation stacks running on the Spacelift platform. If the environment variable is not present a given Spacelift stack, the stack should work like it does today. This would allow customizing tags per stack to facilitate simpler tag management which is crucial for automation, compliance, and audit purposes.
I would expect this to be backwards compatible as well.
Please authenticate to join the conversation.
⬆️ Gathering votes
💡 Feature Requests
CloudFormation
Over 1 year ago
Get notified by email when there are changes.
⬆️ Gathering votes
💡 Feature Requests
CloudFormation
Over 1 year ago
Get notified by email when there are changes.