resource/aws_spot_instance_request: Bump delete timeout to 20mins #3435
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.
This is mainly to address the following test failure:
I was playing with the idea of setting custom, higher timeout inside the test config, but since we get some guarantees that the instance is actually shutting down (i.e. transitioning from
shutting-down
toterminated
) I can't think of any downside of bumping this for everyone.I'm generally against cranking timeouts so high if it is error-based retry where the risk of false positive is much higher. This isn't the case though.