Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws_cloudwatch_metric_alarm does not validate input on alarm_actions #19015

Closed
sprutner opened this issue Oct 5, 2018 · 2 comments
Closed

aws_cloudwatch_metric_alarm does not validate input on alarm_actions #19015

sprutner opened this issue Oct 5, 2018 · 2 comments

Comments

@sprutner
Copy link
Contributor

sprutner commented Oct 5, 2018

Terraform Version

0.11.8

Terraform Configuration Files

resource "aws_cloudwatch_metric_alarm" "down-blue" {
  alarm_name          = "${var.blue_asg_name}-High-CPU-Utilization-LT-10"
  comparison_operator = "LessThanThreshold"
  evaluation_periods  = "${var.scale_down_evaluation_periods}"
  metric_name         = "${var.scaling_metric}"
  namespace           = "AWS/EC2"
  period              = "${var.scale_down_evaluation_period}"
  statistic           = "Average"
  threshold           = "${var.scale_down_threshold}"

  dimensions {
    AutoScalingGroupName = "${var.blue_asg_name}"
  }

  alarm_description = "This metric monitors ec2 cpu utilization"
  **alarm_actions     = ["${aws_autoscaling_policy.down-blue.name}"]**
}

Expected Behavior

Actual Behavior

Steps to Reproduce

  1. Simply put an autoscaling group name in alarm_actions instead of an ARN.

Additional Context

This should be an easy fix if you just use a regex or something to check if it's an ARN being passed in.

@ghost
Copy link

ghost commented Oct 8, 2018

This issue has been automatically migrated to hashicorp/terraform-provider-aws#6092 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#6092.

@ghost
Copy link

ghost commented Apr 1, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 1, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants