Wait for cluster endpoint #193
Merged
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
Try out sleeping for 10s to see if that addresses availability issues. If so, we likely want to make a more correct fix to poll the API endpoint instead.
Instead of always waiting 5 minutes, instead try to hit the cluster endpoint every 5 seconds, continuing on as soon as we can. If we still can't reach it after 5 minutes, we allow the operation to continue (presumably to fail on some other operation).
lukehoban
added
the
impact/no-changelog-required
|
Hi there, could it be that this polling is not respecting the http_proxy setting? |
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.
Wait for up to 300 seconds for cluster endpoint to be reachable.
Fixes #65.