Skip to main content

Managing Dagster+ with Terraform

Early access preview

This feature is currently in an early prototype stage. Functionality and APIs may change as development continues.

You can find the Dagster+ provider in the Terraform Registry. To send feedback and bug reports, please file a GitHub issue.

When to use Terraform​

Terraform is a good fit if your organization already uses infrastructure-as-code tooling or wants to:

  • Automate onboarding — provision deployments, invite users, and assign team permissions in a single workflow
  • Enforce consistency — ensure configuration is identical across environments (e.g. staging and prod have the same alert policies)
  • Audit changes — track who changed what and when through version control and Terraform state
  • Manage at scale — coordinate many deployments, users, or secrets without manual UI work

If you only occasionally adjust settings or are just getting started with Dagster+, the UI is usually simpler.

Getting started​

Prerequisites​

Configure the provider​

terraform {
  required_providers {
    dagsterplus = {
      source  = "dagster-io/dagsterplus"
      version = "~> 0.1"
    }
  }
}

provider "dagsterplus" {
  organization = "my-org"  # subdomain of your Dagster+ URL
}

Set your API token as an environment variable:

export DAGSTER_CLOUD_API_TOKEN="your-api-token"

Initialize Terraform and apply your configuration:

terraform init
terraform apply

Example​

The following example creates a deployment, invites a user, and grants a team access. This is the kind of multi-step workflow that benefits most from automation:

resource "dagsterplus_user" "alice" {
  email = "alice@example.com"
}

resource "dagsterplus_team" "data_engineering" {
  name = "data-engineering"

  deployment_grant {
    deployment = "prod"
    grant      = "EDITOR"
  }

  member {
    user_id = dagsterplus_user.alice.id
  }
}