Until last week 16 feb we created a stack with (ReplicationGroup, ParamGroup, ...) and a set of tags.
Since this week the paramgroup naming has slightly changed and there is no tags to the created resource.
What issue does this bug cause:
tag based policy is broken, without tags the policies do not provide correct permissions
Expected Behavior
When cloudformation creates resources it should add all the tags to it.
Observed Behavior
It still adds the tags to all other resources in the Stack as before, but not the ParamGroup.
ParamGroup resource is still listed in the Stack as a resource belonging to it.
Test Cases
Create ParamGroup such as in the console (UI) with just this template.
AWSTemplateFormatVersion: "2010-09-09"
Description: Test
Resources:
TestPGroup:
Type: AWS::ElastiCache::ParameterGroup
Properties:
CacheParameterGroupFamily: redis7
Properties:
maxmemory-policy: "allkeys-lru"
reserved-memory-percent: "10"
Description: "group which should be tagged"
Name of the resource
AWS::ElastiCache::ParameterGroup
Resource Name
No response
Issue Description
Until last week 16 feb we created a stack with (ReplicationGroup, ParamGroup, ...) and a set of tags. Since this week the paramgroup naming has slightly changed and there is no tags to the created resource.
What issue does this bug cause:
Expected Behavior
When cloudformation creates resources it should add all the tags to it.
Observed Behavior
It still adds the tags to all other resources in the Stack as before, but not the ParamGroup. ParamGroup resource is still listed in the Stack as a resource belonging to it.
Test Cases
Create ParamGroup such as in the console (UI) with just this template.
add any set of tags e.g. { "myTag":"MyValue"}
Other Details
No response