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

Changing aws_autoscaling_group value for default_cooldown forces a new resource #2509

Closed
CpuID opened this issue Jun 26, 2015 · 1 comment · Fixed by #2510
Closed

Changing aws_autoscaling_group value for default_cooldown forces a new resource #2509

CpuID opened this issue Jun 26, 2015 · 1 comment · Fixed by #2510

Comments

@CpuID
Copy link
Contributor

CpuID commented Jun 26, 2015

I can update both health_check_grace_period and default_cooldown via the AWS Console without recreating, this should also be possible via the API I suspect.

    default_cooldown:                   "300" => "240" (forces new resource)

If I feel up to it I'll lodge a PR shortly for this :)

@ghost
Copy link

ghost commented May 2, 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 2, 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

Successfully merging a pull request may close this issue.

1 participant