SNOW-1621763: na+spcs tutorial #14
Closed
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
added 2 commits
October 1, 2024 14:59
sfc-gh-yxu
requested review from
sfc-gh-tvanderkooy,
sfc-gh-bdufour and
sfc-gh-mlewandowski
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 tutorial is based on the existing tutorial(https://docs.snowflake.com/en/developer-guide/native-apps/tutorials/na-spcs-tutorial) and it focuses on the na+spcs upgrade. It will be used for our tech writer Steven Leslie to convert into a public doc.
The purpose of this branch is to record discussion and track the changes, and it may not merge into the main branch.
@sfc-gh-tvanderkooy Could you please confirm it covered the major use cases of the na+spcs upgrades
@sfc-gh-bdufour I was told that we prefer to using snowsql in our tutorial, could you please help.
This guide walks through managing versions of a Snowflake Native App with Snowpark Container Services:
Setup Version
v1.0: An application package is created, along with schemas, roles, and procedures. A Docker-based echo service and UDF are deployed.Upgrade to Version
v1.1(Hotfix): A hotfix changes the service endpoint from public to private. The service's YAML file is updated, and a version upgrade applies the fix.Simulate Upgrade Failure (Version
v2.0): The guide simulates an upgrade failure by introducing an error in the setup script. The system automatically reverts to versionv1.1, keeping the service operational.Fix the Error (Version
v2.1): After fixing the error, the app is successfully upgraded to versionv2.1.Upgrade to Version
v3.0: To create versionv3.0, versionv1is dropped (since only two active versions are allowed), and the upgrade is completed.This tutorial demonstrates managing lifecycle upgrades, dealing with failures, and ensuring service continuity.