aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::SQS::Queue] - [BUG] - resources don't receive the `aws:cloudformation:*` built-in tags / default service-managed auto-tags
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::SQS::Queue
### 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 for customers.
### Expected Behavior
Resources with type `AWS::SQS::Queue`, which are managed as CloudFormations Stacks, should automatically receive the `aws:cloudformation:*` built-in tags / automatic default CFN AutoTags.
### Observed Behavior
When you have an `AWS::SQS::Queue` resource in your stack, it does not get the built-in tags assigned:
- `aws:cloudformation:stack-name`
- `aws:cloudformation:logical-id`
- `aws:cloudformation:stack-id`
### Test Cases
```yaml
Resources:
Queue:
Type: AWS::SQS::Queue
```
### Other Details
_No response_
Contributor guide
Research direction
Start with the provided AWS::SQS::Queue YAML test case and inspect how this repository tracks CloudFormation resource coverage; no source file or test entry point is named. Done means a queue managed by a CloudFormation stack receives aws:cloudformation:stack-name, aws:cloudformation:logical-id, and aws:cloudformation:stack-id automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100