snow spcs service create¶
Note
You can use Snowpark Container Services from Snowflake CLI only if you have the necessary permissions to use Snowpark Container Services.
Creates a new service in the current schema.
Syntax¶
snow spcs service create
<name>
--compute-pool <compute_pool>
--spec-path <spec_path>
--min-instances <min_instances>
--max-instances <max_instances>
--auto-resume / --no-auto-resume
--eai-name <external_access_integrations>
--query-warehouse <query_warehouse>
--tag <tags>
--comment <comment>
--if-not-exists
--connection <connection>
--host <host>
--port <port>
--account <account>
--user <user>
--password <password>
--authenticator <authenticator>
--private-key-file <private_key_file>
--token-file-path <token_file_path>
--database <database>
--schema <schema>
--role <role>
--warehouse <warehouse>
--temporary-connection
--mfa-passcode <mfa_passcode>
--enable-diag
--diag-log-path <diag_log_path>
--diag-allowlist-path <diag_allowlist_path>
--format <format>
--verbose
--debug
--silent
Arguments¶
name
Identifier of the service. For example: my_service.
Options¶
--compute-pool TEXT
Compute pool to run the service on.
--spec-path FILE
Path to service specification file.
--min-instances INTEGER RANGE
Minimum number of service instances to run. Default: 1.
--max-instances INTEGER RANGE
Maximum number of service instances to run.
--auto-resume / --no-auto-resume
The service will automatically resume when a service function or ingress is called. Default: True.
--eai-name TEXT
Identifies External Access Integrations(EAI) that the service can access. This option may be specified multiple times for multiple EAIs.
--query-warehouse TEXT
Warehouse to use if a service container connects to Snowflake to execute a query without explicitly specifying a warehouse to use.
--tag NAME=VALUE
Tag for the service.
--comment TEXT
Comment for the service.
--if-not-exists
Only apply this operation if the specified object does not already exist. Default: False.
--connection, -c, --environment TEXT
Name of the connection, as defined in your
config.toml
. Default:default
.--host TEXT
Host address for the connection. Overrides the value specified for the connection.
--port INTEGER
Port for the connection. Overrides the value specified for the connection.
--account, --accountname TEXT
Name assigned to your Snowflake account. Overrides the value specified for the connection.
--user, --username TEXT
Username to connect to Snowflake. Overrides the value specified for the connection.
--password TEXT
Snowflake password. Overrides the value specified for the connection.
--authenticator TEXT
Snowflake authenticator. Overrides the value specified for the connection.
--private-key-file, --private-key-path TEXT
Snowflake private key file path. Overrides the value specified for the connection.
--token-file-path TEXT
Path to file with an OAuth token that should be used when connecting to Snowflake.
--database, --dbname TEXT
Database to use. Overrides the value specified for the connection.
--schema, --schemaname TEXT
Database schema to use. Overrides the value specified for the connection.
--role, --rolename TEXT
Role to use. Overrides the value specified for the connection.
--warehouse TEXT
Warehouse to use. Overrides the value specified for the connection.
--temporary-connection, -x
Uses connection defined with command line parameters, instead of one defined in config. Default: False.
--mfa-passcode TEXT
Token to use for multi-factor authentication (MFA).
--enable-diag
Run python connector diagnostic test. Default: False.
--diag-log-path TEXT
Diagnostic report path. Default: <temporary_directory>.
--diag-allowlist-path TEXT
Diagnostic report path to optional allowlist.
--format [TABLE|JSON]
Specifies the output format. Default: TABLE.
--verbose, -v
Displays log entries for log levels
info
and higher. Default: False.--debug
Displays log entries for log levels
debug
and higher; debug logs contains additional information. Default: False.--silent
Turns off intermediate output to console. Default: False.
--help
Displays the help text for this command.
Usage notes¶
You can optionally choose to run more than one instance of your service. Each service instance is a collection of containers, as defined in the service specification file, that run together on a node in your compute pool. If you choose to run multiple instances of a service, a load balancer manages incoming traffic.
Examples¶
snow spcs service create "my-service" --compute-pool "pool_1" --spec-path "/some-dir/echo-speck.yaml"