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

AWS::ElasticLoadBalancingV2::ListenerRule resources don’t receive the aws:cloudformation built-in tags / default AutoTags

Open
#1,437 2 comments 15 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::ElasticLoadBalancingV2::ListenerRule

### Resource Name

_No response_

### 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

All stack resources of type `AWS::ElasticLoadBalancingV2::ListenerRule` 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::ElasticLoadBalancingV2::ListenerRule` resource in your stack, it does not get assigned the built-in tags: `aws:cloudformation:stack-name`, `aws:cloudformation:logical-id` and `aws:cloudformation:stack-id`

### Test Cases

deploy a 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.

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

No repository files or tests are identified. Start by deploying a stack containing an AWS::ElasticLoadBalancingV2::ListenerRule, using an AWS documentation sample, and inspect its tags in the console. Confirm whether the aws:cloudformation:stack-name, logical-id, and stack-id tags are absent, then verify the expected Drift Detection handling for those tags.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.