move to 30 minute timeout for aws ecs wait services-stable #3306
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 moves the
aws ecs wait services-stableto having a 30 minute timeout. I don't have any data on if 30 minutes is ideal but anecdotally based on requests and internet posts 10 minutes may not be enough.This is in response to issue [ECS] Waiter: Increase ServicesStable Waiter Time to "x" Time (30 or 60 minutes?) and, previously, #3305 .
I do believe the appropriate long term solution is to expose this variable - a ticket for the AWS CLI has already been opened, originally on April 17, 2015 (aws/aws-cli#1295).