Fix aws_autoscaling_group default_cooldown in case explicitly set to 0 #8419
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GetOk will compare the value to the default zero value of a
type. When the default_cooldown is set to 0, the value matches the default zero
value of the type Integer and will be ignored for the api request.
Normally not a problem, but in this case, this results in an default_cooldown
of 300s on AWS side.
This change will use getOkExists, which doesn't compare to the default zero value.
Community Note
Fixes #8412