snow dbt deploy¶
Note
Some features described on this page require a dbt project object that uses the mutable live version. To get a live-version object, opt in to the 2026_06 behavior change bundle or ask your Snowflake account representative to enable the separate single live version feature. Then create or replace the object, or migrate an existing versioned object with SYSTEM$MIGRATE_DBT_PROJECT. For details, see dbt Projects on Snowflake: dbt project objects migrate to a single mutable live version.
Upload local dbt project files and create or update a dbt project object on Snowflake.
Syntax¶
Arguments¶
nameRequired
Identifier of the DBT Project; for example: my_pipeline.
Options¶
--source TEXTPath to directory containing dbt files to deploy. Defaults to current working directory.
--profiles-dir TEXTPath to directory containing profiles.yml or dbt_projects_profiles.yml (the latter takes precedence and is staged under its own name). Defaults to directory provided in –source or current working directory.
--env-file-dir TEXTPath to directory containing env.yml. If provided, the file is injected into the deployed project root, overwriting any env.yml present in –source.
--force / --no-forceRecreates the dbt project object with CREATE OR REPLACE DBT PROJECT. This removes all existing versions and run history. Default: False.
--default-target TEXTDefault target for the dbt project. Mutually exclusive with –unset-default-target.
--unset-default-targetUnset the default target for the dbt project. Mutually exclusive with –default-target. Default: False.
--default-env TEXTDefault environment for the dbt project. Selects the environment block from env.yml that the project compiles and executes with by default. Mutually exclusive with –unset-default-env.
--unset-default-envUnset the default environment for the dbt project. Mutually exclusive with –default-env. Default: False.
--external-access-integration TEXTExternal access integration to be used by the dbt object.
--install-local-depsSets EXTERNAL_ACCESS_INTEGRATIONS = () on the dbt project. Snowflake still runs dbt deps at compile; Hub or Git packages in packages.yml still need network access. Default: False.
--dbt-version TEXTdbt Core version to use for the project, for example ’1.10.15’. Full list of supported versions can be found at https://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-dbt-core-versions.
--default-writeback / --no-default-writebackSet the writeback default persisted on the dbt project. Omit to leave the existing setting unchanged.
--auto-compile / --no-auto-compileSet whether the dbt project is compiled on deploy; persisted on the project and applied to subsequent deploys until changed. Omit to leave the existing setting unchanged.
--git-commit TEXTGit commit hash to record in last_deployed_from metadata when deploying from a plain stage (e.g. SnowCLI temp stage). In GitHub Actions it is auto-detected when not provided.
--git-branch TEXTGit branch name to record in last_deployed_from metadata when deploying from a plain stage (e.g. SnowCLI temp stage). In GitHub Actions it is auto-detected when not provided.
--git-url TEXTGit repository URL to record in last_deployed_from metadata when deploying from a plain stage (e.g. SnowCLI temp stage). In GitHub Actions it is auto-detected from GITHUB_SERVER_URL and GITHUB_REPOSITORY when not provided.
--connection, -c, --environment TEXTName of the connection, as defined in your
config.tomlfile. Default:default.--host TEXTHost address for the connection. Overrides the value specified for the connection.
--port INTEGERPort for the connection. Overrides the value specified for the connection.
--protocol TEXTProtocol to use for the connection, for example
https. Overrides the value specified for the connection.--account, --accountname TEXTName assigned to your Snowflake account. Overrides the value specified for the connection.
--user, --username TEXTUsername to connect to Snowflake. Overrides the value specified for the connection.
--password TEXTSnowflake password. Overrides the value specified for the connection.
--authenticator TEXTSnowflake authenticator. Overrides the value specified for the connection.
--workload-identity-provider TEXTWorkload identity provider (AWS, AZURE, GCP, OIDC). Overrides the value specified for the connection.
--private-key-file, --private-key-path TEXTSnowflake private key file path. Overrides the value specified for the connection.
--token TEXTOAuth token to use when connecting to Snowflake.
--token-file-path TEXTPath to file with an OAuth token to use when connecting to Snowflake.
--database, --dbname TEXTDatabase to use. Overrides the value specified for the connection.
--schema, --schemaname TEXTDatabase schema to use. Overrides the value specified for the connection.
--role, --rolename TEXTRole to use. Overrides the value specified for the connection.
--warehouse TEXTWarehouse to use. Overrides the value specified for the connection.
--temporary-connection, -xUses a connection defined with command-line parameters, instead of one defined in config. Default: False.
--mfa-passcode TEXTToken to use for multi-factor authentication (MFA).
--enable-diagWhether to generate a connection diagnostic report. Default: False.
--diag-log-path TEXTPath for the generated report. Defaults to system temporary directory. Default: <system_temporary_directory>.
--diag-allowlist-path TEXTPath to a JSON file that contains allowlist parameters.
--oauth-client-id TEXTValue of client id provided by the Identity Provider for Snowflake integration.
--oauth-client-secret TEXTValue of the client secret provided by the Identity Provider for Snowflake integration.
--oauth-authorization-url TEXTIdentity Provider endpoint supplying the authorization code to the driver.
--oauth-token-request-url TEXTIdentity Provider endpoint supplying the access tokens to the driver.
--oauth-redirect-uri TEXTURI to use for authorization code redirection.
--oauth-scope TEXTScope requested in the Identity Provider authorization request.
--oauth-disable-pkceDisables Proof Key for Code Exchange (PKCE). Default:
False.--oauth-enable-refresh-tokensEnables a silent re-authentication when the actual access token becomes outdated. Default:
False.--oauth-enable-single-use-refresh-tokensWhether to opt-in to single-use refresh token semantics. Default:
False.--client-store-temporary-credentialStore the temporary credential.
--secondary-roles TEXTSecondary roles mode applied when the session starts. Supported values are
ALLandNONE; passNONEto run the session only with the primary role.--server-session-keep-aliveKeep the session active indefinitely, even if there is no activity from the user.
--format [TABLE|JSON|JSON_EXT|CSV]Specifies the output format. [env var: SNOWFLAKE_CLI_OUTPUT_FORMAT | config: cli.output_format]. Default: TABLE.
--verbose, -vDisplays log entries for log levels
infoand higher. Default: False.--debugDisplays log entries for log levels
debugand higher; debug logs contain additional information. Default: False.--silentTurns off intermediate output to console. Default: False.
--enhanced-exit-codesDifferentiate exit error codes based on failure type. Default: False.
--decimal-precision INTEGERNumber of decimal places to display for decimal values. Uses Python’s default precision if not specified. [env var: SNOWFLAKE_DECIMAL_PRECISION].
--helpDisplays the help text for this command.
Usage notes¶
The snow dbt deploy command uploads local files to a temporary stage and either creates a new object or replaces the existing object’s live version in a single operation. A valid dbt project object must contain dbt_project.yml and one of the supported profile files:
dbt_project.yml: A standard dbt configuration file that specifies the profile to use.- dbt_projects_profiles.yml or
profiles.yml: A dbt connection profile definition referenced indbt_project.yml. The selected profile file must define the database, role, schema, and type. If both files are present, Snowflake usesdbt_projects_profiles.ymland ignoresprofiles.ymlduring deployment, compilation, and subsequent commands. - By default, dbt Projects on Snowflake uses your target schema (
target.schema) specified from your dbt environment or profile. When you execute a dbt project object, dbt attempts to create the target schema specified in the profile file if it doesn’t already exist. For more information, see Understand schema generation and customization.
A profile defines target, outputs, and per-output fields such as database, role, schema, warehouse, and type: snowflake.
When snow dbt deploy runs in GitHub Actions, Snowflake CLI automatically captures the commit and branch. For other CI runners, explicitly pass --git-commit and --git-branch to preserve this source metadata.
Warning
Don’t use --force unless you intentionally want to recreate the dbt project object. In snow dbt deploy, --force runs CREATE OR REPLACE DBT PROJECT, which may remove run history.
Examples¶
-
Deploy a dbt project named
jaffle_shop: -
Deploy a project with automatic compilation disabled. Useful for optimizing Slim CI workflows:
-
Deploy from a CI runner and record the source commit and branch. Snowflake CLI captures this information automatically when deploying from GitHub Actions:
-
Deploy a project named
jaffle_shopfrom a specified directory, using a profile file from a separate directory: -
Deploy a project named
jaffle_shopfrom a specified directory, supplying a profile file from outside the project, setting a default target, and enabling external access integrations: -
Deploy a project named
jaffle_shopand set a specific dbt runtime version: -
Deploy a project named
jaffle_shop, pull in anenv.ymlfile from a separate directory, and set the default environment for compilation and later executions: