Deployment environments

5X Managed dbt Core™ enables reliable, user-friendly and scalable solutions for deploying data assets for the end user. You can deploy dbt projects to ensure the production pipeline is efficiently maintained. Run Jobs using scheduled triggers to identify the root cause of errors. Users can Deploy Jobs and CI Job types based on their need for Job runs. CI jobs implement continuous integration in production to ensure automated modified changes.

A dbt project supports multiple Deployment environments to help users deploy jobs in production. A default deployment environment is created when you build a project. Its environment cits environment configures the target based on the schema settings of the vendor connection. Users can run jobs in production from the deployment environments.

Users can access and manage the deployment environment on 5X Managed dbt Core™ as follows:

  1. Navigate to Environments to check the deployment environments on your dbt project. You can also create a deployment environment by clicking on Create Environment.

  2. Alternatively, when setting up your dbt project, users need to configure the default deployment environment. Refer to set up a dbt project to learn more.

  3. Users can update their default deployment settings from Project Settings.

Note

Users can update Project Settings to modify development environments only, and cannot update deployment environments.

Set up a deployment environment

Prerequisites

  • Users must configure the warehouse connection of the dbt project to create environments.

To set up a deployment environment, follow the steps below:

  1. Navigate to Environments and click Create Environment to the right.

  1. Configure the general settings, deployment connection and deployment credentials of the development environment:

  • General settings: Enter the development environment name, select the dbt version and the environment type. Choose to run your modified code on a custom branch of Git using the checkbox.

Setting the default target will mean dbt will access the default target named dev and the modified changes will be built in your development target.

Users can check the target-path directory from the dbt_project.yml project file on the Console. The target-path directory stores compiled SQL files.

  • Deployment connection and credentials: Set up the warehouse connection required for the 5X managed dbt core instance to build on top of the warehouse connection. Enter the deployment credentials required for the 5X managed dbt core instance to access the schema. The deployment credentials depend on the warehouse connection set up for the dbt project.

Deployment credentials depend on the dbt project connection. General settings parameters are common across all configurations. The deployment connection and credentials have the following parameters:

  • Snowflake connection: A dbt project with a Snowflake connection requires deployment connection and credentials to configure the Snowflake account warehouse, database and schema details.

Refer to Parameters to check the parameter specifications.

Users can also select the authentication type from Password or Key Pair. Key pair authentication ​​uses a public-private key pair to establish secure connections, eliminating the need for passwords. This ensures a private key is securely stored, while the public key is shared with the server. You can also opt to add private key passphrase.

  • Databricks connection: The parameters are the same as required when you set up a Databricks connection for the project. Refer to Parameters to check the specifications.

  • Google BigQuery connection: The deployment connection parameters are the same as when you set up a Google BigQuery connection for the project.

Click Save to set up your development environment. You can check and update the development environment from Environments.

Last updated