You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :)
The text was updated successfully, but these errors were encountered:
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
locked and limited conversation to collaborators
May 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If I feel up to it I'll lodge a PR shortly for this :)
The text was updated successfully, but these errors were encountered: