Use update
timeout value in ec2_instance_state
if greater than hard-coded instanceStopTimeout
or instanceStartTimeout
#41642
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.
Description
The
update
timeout isn't used when starting/stopping an EC2 instance, instead the hard-codedinstanceStopTimeout
andinstanceStartTimeout
are used. This PR uses theupdate
timeout value if greater than either one of constant values. This is useful when dealing with large EC2 instances (e.g.p3dn.24xlarge
) that take a very long time to start/stop.