-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNOW-1621763 update example for na + spcs upgrade #12
base: main
Are you sure you want to change the base?
Conversation
@@ -1,5 +1,4 @@ | |||
set -e | |||
snow sql -f "prepare/spcs_setup.sql" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do not need this anymore. Please see https://snowflakecomputing.atlassian.net/browse/SNOW-1527720
95dc76e
to
384b058
Compare
spcs-three-tier/app/setup.sql
Outdated
--wait for 300 seconds, but it will stop if two services have READY status, | ||
-- or any of the services has the FAILED status. | ||
select system$wait_for_services(300, 'app_public.backend', 'app_public.frontend'); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Handle the failure to create service
Should throw exception to force app failure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know what the best practice is from the NA+SPCS team? That's what we want to have here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had a test and found out that if the service was not available or not ready, it will fail
No description provided.