aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Make type of Tags property consistent among services

Open
#248 0 comments 6 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

Some resources like `AWS::Glue::Job` or `AWS::Glue::Trigger` expect a Json (Dict) as Tags Property while others like `AWS::S3::Bucket` or `AWS::SQS::Queue` expect a List. Use the more compact Dict syntax in all Tags Properties.

When using tags in several place on a YAML file it's useful to use anchor/alias. With two types of Tags it's necessary to define two series of tags, one for properties that expect Dict and one for properties that expect List.

Example of Dict and List syntax for the same 5 tags:
```
tagDict: &tagDict
global.app: ${self:custom.service}
global.env: dev
global.opco: axa-be
global.project: ${self:custom.project}
global.DCS: datalab

tagList: &tagList
- Key: global.app
Value: ${self:custom.service}
- Key: global.env
Value: dev
- Key: global.opco
Value: axa-be
- Key: global.project
Value: ${self:custom.project}
- Key: global.DCS
Value: datalab
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.