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: autoscaling_group health_check_grace_period loads a new instance #1679

Closed
mzupan opened this issue Apr 25, 2015 · 2 comments
Closed

AWS: autoscaling_group health_check_grace_period loads a new instance #1679

mzupan opened this issue Apr 25, 2015 · 2 comments

Comments

@mzupan
Copy link
Contributor

mzupan commented Apr 25, 2015

If you edit the grace period for a autoscaling group it will kill the old one and create a new one. You should be able to edit this without killing your current auto scale group. At least you can on the web UI

-/+ aws_autoscaling_group.rabbit
    availability_zones.#:               "3" => "3"
    availability_zones.1305112097:      "us-east-1b" => "us-east-1b"
    availability_zones.2762590996:      "us-east-1d" => "us-east-1d"
    availability_zones.986537655:       "us-east-1c" => "us-east-1c"
    default_cooldown:                   "300" => "<computed>"
    desired_capacity:                   "1" => "1"
    force_delete:                       "true" => "1"
    health_check_grace_period:          "2000" => "200" (forces new resource)
@mitchellh
Copy link
Contributor

Thanks for the fix!

@ghost
Copy link

ghost commented May 3, 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 May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants