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

Failure configuring AWS Autoscaling Policy with adjustment-type ExactCapacity and scaling-adjustment from 1 to 0 #6276

Closed
hgontijo opened this issue Apr 21, 2016 · 4 comments

Comments

@hgontijo
Copy link
Contributor

Terraform Version

v0.6.14

Affected Resource(s)

aws_autoscaling_policy

Terraform Configuration Files

...
resource "aws_autoscaling_policy" "ci_scaledown_conf" {
    name = "asg-scaledown"
    scaling_adjustment = 0
    adjustment_type = "ExactCapacity"
    cooldown = 30
    autoscaling_group_name = "${aws_autoscaling_group.ci_asg_conf.name}"
}
...

Debug Output

https://gist.github.com/hgontijo/5005e78944ccffe8b87410269804680e

Panic Output

n/a

Expected Behavior

ASG policy scaling_adjustment to be set as "1" => "0".
This configuration can be done via AWS Console or cli: https://gist.github.com/hgontijo/14ad093e6a305b1ee58fba24fabf1164

Actual Behavior

It fails.

Steps to Reproduce

Configure ASG Policy hcl with:
scaling_adjustment = 0
adjustment_type = "ExactCapacity"

terraform apply

Important Factoids

n/a

References

n/a

@justintime
Copy link

I can confirm this bug is still present today in 0.7.1

@denniswebb
Copy link
Contributor

I have a PR in for this if it can just get a quick review.

@catsby
Copy link
Contributor

catsby commented Oct 21, 2016

Fixed in #6276, thanks!

@catsby catsby closed this as completed Oct 21, 2016
@ghost
Copy link

ghost commented Apr 21, 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 21, 2020
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

5 participants