cloudwatch_metric_alarm should allow datapoints_to_alarm to be 0

[onlynone]

Terraform and AWS Provider Version

Terraform v1.9.8
on darwin_arm64
+ provider registry.terraform.io/hashicorp/aws v6.24.0

Your version of Terraform is out of date! The latest version
is 1.14.1. You can update by downloading from https://www.terraform.io/downloads.html

Affected Resource(s) or Data Source(s)

• cloudwatch_metric_alarm

Expected Behavior

You should be able to specify:

  datapoints_to_alarm = 0

In order to get the default behavior of datapoints_to_alarm being the same as evaluation_periods. If you don't set a value for datapoints_to_alarm initially and then set one to some positive integer, terraform will report the change like:

  # aws_cloudwatch_metric_alarm.example will be updated in-place
  ~ resource "aws_cloudwatch_metric_alarm" "example" {
      ~ datapoints_to_alarm                   = 0 -> 1

Indicating that it did use 0 for the default value. And looking at the alarm in the AWS console, under "Conditions" -> "Datapoints to alarm", it says "N out of N" where N is whatever you have evaluation_periods set to.

Actual Behavior

You get the error Error: expected datapoints_to_alarm to be at least (1), got 0

Relevant Error/Panic Output

Sample Terraform Configuration

Click to expand configuration

resource "aws_cloudwatch_metric_alarm" "example" {
  datapoints_to_alarm = 0
}

Steps to Reproduce

1. Specify a cloudwatch_metric_alarm resource with datapoints_to_alarm = 0
2. Run terraform plan or terraform apply

Debug Logging

No response

GenAI / LLM Assisted Development

n/a

Important Facts and References

No response

Would you like to implement a fix?

No

[github-actions]

Community Guidelines

This comment is added to every new Issue to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Issue and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.