Cloud Stacks: Better "wait for readiness" #1545
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
Seems like HEAD calls on the instance's URL doesn't work anymore. Instead, we can hit `/api/health` which gives us a better idea Then there's the cloud_stack_service_account resources which require an active instance but just 503 if it's not ready. Let's wait for the stack readiness before doing anything on those resources
|
In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically. |
K-Phoen
approved these changes
May 7, 2024
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.
Seems like HEAD calls on the instance's URL doesn't work anymore. Instead, we can hit
/api/healthwhich gives us a better ideaThen there's the cloud_stack_service_account resources which require an active instance but just 503 if it's not ready. Let's wait for the stack readiness before doing anything on those resources