This guide is applicable to Dagster Cloud.
In Dagster Cloud, there are two types of deployments:
This guide will focus on full deployments, hereafter referred to simply as deployments.
Deployments are standalone environments, allowing you to operate independent instances of Dagster with separately managed permissions.
When a Dagster Cloud organization is created, a single deployment named prod
will also be created. To create additional deployments, an Enterprise plan is required.
Each deployment can have one or multiple code locations.
Concerned about testing environments? We recommend using Branch Deployments to test your changes, even if you're able to create additional deployments. Branch deployments are available for all Dagster Cloud users, regardless of plan.
Refer to the Branch Deployment docs for more info, or the Testing against production using Branch Deployments guide for a real-world example.
In Dagster Cloud, you can view and switch between deployments using the deployment switcher:
To view all deployments, click View all deployments.
Organization Admin permissions are required to create deployments. Additionally, note that creating multiple deployments requires an Enterprise plan.
To create a deployment:
Organization Admin permissions are required to delete deployments. Additionally, note that deleting a deployment also deletes all its associated data, including code locations, jobs, schedules, and sensors.
To delete a deployment:
Organization Admin permissions are required to modify deployment settings.
Deployment settings can be configured in the Dagster Cloud interface or using the dagster-cloud CLI. Refer to the deployment settings reference for more info about individual settings.