Workflow: Develop an app with containers¶
This topic describes the general workflow for creating a Snowflake Native App with Snowpark Container Services.
Understand Snowpark Container Services and the Snowflake Native App Framework¶
Before beginning to develop a Snowflake Native App with Snowpark Container Services
Ensure that you are familiar with Snowpark Container Services and the Snowflake Native App Framework.
The following tutorials are available for these Snowflake products:
Review About apps with containers to understand how Snowflake Native App with Snowpark Container Services works.
Review Costs associated with apps with containers to understand the costs associated with developing, publishing, and using an app with containers.
Create the containers and services to be managed by an app.¶
The first step in developing an app with containers is to set up the required containers and services using Snowpark Container Services.
The basic workflow for using Snowpark Container Services is:
Create a repository to store container images.
This repository exists in the provider account and maintains the container images required by the app. See Create an image repository
Copy the container images to the image repository.
After creating the image repository, providers must upload the container images used by the application. Snowpark Container Services support using Docker commands to perform the upload.
See Upload container images to the image repository for more information.
Create a service specification file.
The service specification file is a YAML file used to configure and run services within Snowpark Container Services. Snowflake Native App with Snowpark Container Services includes this file within the application package.
See Create the service specification file for more information.
Configure block storage and snapshots.
If the services in your app require using block storage, create a
spec.volumes
in your service specification file.See Using block storage volumes with services for more information.
Upload the required files to a stage.
To make the service specification file accessible to the application package, providers must upload it to the stage used to store other files required by the application package.
See Staging data files from a local file system and Staging files using Snowsight for more information on uploading files to a stage.
Note
If you are using the Snowflake CLI, you are not required to upload the files to a stage.
Develop and publish a Snowflake Native App with Snowpark Container Services¶
The workflow for developing and publishing an app with containers is similar to the workflow for any Snowflake Native App. However, within each stage of the workflow there are differences.
The following is a typical workflow for developing and publishing an app with containers:
Create the manifest file for the app.
The manifest file for an app with containers includes configuration information about the containers included in the app. See Create the manifest file for an app with containers for more information.
Create the setup script for the app.
The specific contents of the setup script depend on the requirements of the app. For general information on creating the setup script for an app, see Create a setup script.
Within the setup script you can create the following objects that are specific to a Snowflake Native App with Snowpark Container Services:
You can also add other objects that are part of any Snowflake Native App, including:
Warehouses
External access integrations
Secrets
Create the application package.
The process of creating an application package for an app with containers is the same as other apps. See Create an application package for more information.
Publish the app
Publishing an app as a private listing or on the Snowflake Marketplace is the same as other apps. See Share an app with consumers for more information.