aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::APS::AnomalyDetector] - [Docs] - Alias max length differs from API doc
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
Other
### Resource name
AWS::APS::AnomalyDetector
### Reference Link
https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-aps-anomalydetector.html
### Details
[CloudFormation resource docs](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-aps-anomalydetector.html) state `Maximum: 128`.
[API docs](https://docs.aws.amazon.com/prometheus/latest/APIReference/API_CreateAnomalyDetector.html) however state `Maximum length of 64.`
Contributor guide
Research direction
Start with the CloudFormation resource documentation and the linked AWS Prometheus CreateAnomalyDetector API documentation. Verify the conflicting Alias maximum lengths, then update the CloudFormation documentation to match the authoritative value; the work is done when the resource and API references agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100