Changed waiter.config.delay from 5 seconds to 10 seconds #2761
Conversation
This file contains 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
The documentation below mentions the following with regards to: aws cloudformation wait stack-create-complete [1] [1] http://docs.aws.amazon.com/cli/latest/reference/cloudformation/wait/stack-create-complete.html "Wait until stack status is CREATE_COMPLETE. It will poll every 30 seconds until a successful state has been reached. This will exit with a return code of 255 after 120 failed checks." This should be technically be 30 seconds not 5 seconds or 10 seconds because: 120 calls at 30 seconds intervals will equal 3600 seconds/1 hour until the "Max attempts exceeded" which to confirms with CloudFormations 1 hour* timeout. I understand that it is a fine line between performance (speed) and consistency, but unfortunately some services like CloudFront take time to build.
This was referenced Aug 14, 2017
Closed
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.
The documentation below mentions the following with regards to: aws cloudformation wait stack-create-complete [1]
[1] http://docs.aws.amazon.com/cli/latest/reference/cloudformation/wait/stack-create-complete.html
"Wait until stack status is CREATE_COMPLETE. It will poll every 30 seconds until a successful state has been reached.
This will exit with a return code of 255 after 120 failed checks."
This should be technically be 30 seconds not 5 seconds or 10 seconds because:
120 calls at 30 seconds intervals will equal 3600 seconds/1 hour until the "Max attempts exceeded" which to confirms with CloudFormations 1 hour* timeout.
I understand that it is a fine line between performance (speed) and consistency, but unfortunately some services like CloudFront take time to build.