Open rgoltz opened 1 year ago
Confirmed. No service-managed tags added to AWS::ElasticLoadBalancingV2::ListenerRule resource.
Test code
lb = elbv2.ApplicationLoadBalancer(self, "LB",
vpc=vpc,
internet_facing=True
)
asg = autoscaling.AutoScalingGroup(self, "ASG",
vpc=vpc,
instance_type=ec2.InstanceType.of(ec2.InstanceClass.BURSTABLE2,
ec2.InstanceSize.MICRO),
machine_image=ec2.AmazonLinuxImage()
)
listener = lb.add_listener("Listener",
port=80,
# 'open: true' is the default, you can leave it out if you want. Set it
# to 'false' and use `listener.connections` if you want to be selective
# about who can access the load balancer.
open=True
)
# Create an AutoScaling group and add it as a load balancing
# target to the listener.
listener.add_targets("ApplicationFleet",
port=8080,
targets=[asg]
)
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
andaws: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