[Bug]: Incorrect configuration after deploying aws_cloudwatch_metric_alarm for anomaly detectors #33515
Labels
bug
Addresses a defect in current functionality.
service/cloudwatch
Issues and PRs that pertain to the cloudwatch service.
Terraform Core Version
1.4.2
AWS Provider Version
5.11.0
Affected Resource(s)
aws_cloudwatch_metric_alarm
Expected Behavior
After provisioning the metric based on Anomaly Detector , One should be able to edit / delete the model clicking graphed metrics -> anomaly detection band
as shown below
Also when similar metric is provisioned using AWS CLI or Cloud formation there is a relationship between Anomaly Detector and Base metric which is not visible for the one provisioned using Terraform. See image below for same metric provisioned from AWS CLI or Cloudformation
Actual Behavior
As shown in image below the visual relationship between Anomaly Detector and Base Metric (on which Anomaly detector is based) is missing . Also there is no way one can Edit or Delete the model due to this
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
Please note that changing the order of e1 and m1 in above example does not register as a config change.
If I provision similar metric using CloudFormation or AWS CLI (putMetricAlarm) it works OK
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: