[AWS::ECR::Repository] - [BUG] - resources don't receive the aws:cloudformation built-in tags / default service-managed auto-tags

[rgoltz]

Name of the resource

AWS::ECR::Repository

Issue Description

To find the right CloudFormation Stack, where a AWS resource is defined/maintained aws:cloudformation:* built-in tags are needed. This is an important function in day-to-day business.

Expected Behavior

Resources with type AWS::ECR::Repository, which are managed as CloudFormations Stacks, should automatically receive the aws:cloudformation:* built-in tags / automatic default CFN AutoTags.

Furthermore those aws:cloudformation:* built-in tags must be handled by CloudFormation Drift-Detection correctly (hence, aws:cloudformation:* tags are not a drift)

Observed Behavior

When you have an AWS::ECR::Repository resource in your stack, it does not get the built-in tags assigned: aws:cloudformation:stack-name, aws:cloudformation:logical-id and aws:cloudformation:stack-id

Test Cases

Deploy a CloudFormation stack containing this resource named above (e.g. sample from AWS docs) and check the tags on the console. You can't see aws:cloudformation:* built-in tags.

I've re-tested it right now in eu-central-1 region. No tags aws:cloudformation:* are added to the ECS Service resource.

Other Details

In the area of AWS ECS/ECR Services the resource AWS::ECS::Cluster already receiving aws:cloudformation:* auto-tags.

Furthermore, there is already an open issue in cloudformation-coverage-roadmap repo aws-cloudformation/cloudformation-coverage-roadmap#1280 since 2022.