diff --git a/docs/docs-beta/docs/dagster-plus/deployment/code-locations/code-location-history.md b/docs/docs-beta/docs/dagster-plus/deployment/code-locations/code-location-history.md index f7e080d785acb..33c575030c05a 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/code-locations/code-location-history.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/code-locations/code-location-history.md @@ -1,12 +1,8 @@ --- title: "Code location history and rollbacks" -displayed_sidebar: "dagsterPlus" sidebar_position: 100 -sidebar_label: "Code location history and rollbacks" --- -# Code location history and rollbacks - Dagster+ automatically tracks metadata every time a code location is loaded. This can be used to understand when changes have been made, and what those changes were. In addition, this metadata can be used to quickly redeploy an older version.
@@ -54,4 +50,4 @@ If you notice an issue with newly deployed code, or your code fails to deploy su ## Next steps - Learn more about [Code Locations](/dagster-plus/deployment/code-locations) -- Learn how to [Alert when a code location fails to load](/dagster-plus/features/alerts#alerting-when-a-code-location-fails-to-load) +- Learn how to [Alert when a code location fails to load](/dagster-plus/features/alerts/creating-alerts#alerting-when-a-code-location-fails-to-load) diff --git a/docs/docs-beta/docs/dagster-plus/deployment/code-locations/dagster-cloud-yaml.md b/docs/docs-beta/docs/dagster-plus/deployment/code-locations/dagster-cloud-yaml.md new file mode 100644 index 0000000000000..7790f2cf5230a --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/code-locations/dagster-cloud-yaml.md @@ -0,0 +1,7 @@ +--- +title: dagster_cloud.yaml reference +sidebar_position: 200 +unlisted: true +--- + +{/* TODO move content from https://docs.dagster.io/dagster-plus/managing-deployments/dagster-cloud-yaml */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/code-locations/index.md b/docs/docs-beta/docs/dagster-plus/deployment/code-locations/index.md index ad60593d0bfb4..facde90edf2aa 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/code-locations/index.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/code-locations/index.md @@ -1,11 +1,8 @@ --- title: "Code locations" -displayed_sidebar: "dagsterPlus" -sidebar_position: 50 +sidebar_position: 40 --- -# Code locations - Separate code locations allow you to deploy different projects that still roll up into a single Dagster+ deployment with one global lineage graph. This guide will cover three options for adding a new code location: @@ -237,4 +234,4 @@ The monorepo should have CI/CD configured to deploy your changes and add or upda ## Next steps - After adding a code location, you may want to setup access controls -- You may want to add additional configuration to your code location. This configuration will vary by agent type, but see examples for [setting default resource limits for Kubernetes](/dagster-plus/deployment/hybrid/agents/kubernetes) or [changing the IAM role for ECS](/todo). +- You may want to add additional configuration to your code location. This configuration will vary by agent type, but see examples for [setting default resource limits for Kubernetes](/dagster-plus/deployment/deployment-types/hybrid/kubernetes) or [changing the IAM role for ECS](/todo). diff --git a/docs/docs-beta/docs/dagster-plus/deployment/code-requirements.md b/docs/docs-beta/docs/dagster-plus/deployment/code-requirements.md index 1fba813927a18..ad75ee2411dd0 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/code-requirements.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/code-requirements.md @@ -1,8 +1,7 @@ --- title: 'Dagster+ code requirements' -displayed_sidebar: 'dagsterPlus' sidebar_label: "Code requirements" -sidebar_position: 100 +sidebar_position: 10 --- Your Dagster project must meet a few requirements to run in Dagster+. @@ -34,7 +33,7 @@ To work with Dagster+, your Dagster code: ## Hybrid deployment requirements -If you're using [Hybrid Deployment](/dagster-plus/deployment/hybrid), there are a few additional requirements. +If you're using [Hybrid Deployment](/dagster-plus/deployment/deployment-types/hybrid), there are a few additional requirements. - **If using an Amazon Elastic Container Service (ECS), Kubernetes, or Docker agent**, your code must be packaged into a Docker image and pushed to a registry your agent can access. Dagster+ doesn't need access to your image - the agent only needs to be able to pull it. diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-settings.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-settings.md deleted file mode 100644 index bbfa62beba985..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/deployment-settings.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Deployment settings" -displayed_sidebar: "dagsterPlus" -sidebar_label: "Deployment settings" -unlisted: true -sidebar_position: 300 ---- - -# Deployment settings diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types.md deleted file mode 100644 index 383e5b696c920..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: Deployment types -unlisted: true -sidebar_position: 400 ---- - -# Deployment types diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/configuration-reference.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/configuration-reference.md new file mode 100644 index 0000000000000..62d9f00dcf50d --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/configuration-reference.md @@ -0,0 +1,7 @@ +--- +title: Configuration reference +sidebar_position: 400 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/amazon-ecs/configuration-reference */} diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc.md new file mode 100644 index 0000000000000..edddddfbded2f --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc.md @@ -0,0 +1,7 @@ +--- +title: Existing VPC setup +sidebar_position: 200 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/amazon-ecs/creating-ecs-agent-existing-vpc */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/index.md new file mode 100644 index 0000000000000..ade5c5b935ffa --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/index.md @@ -0,0 +1,8 @@ +--- +title: Amazon ECS agent +sidebar_position: 50 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/manual-provision.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/manual-provision.md new file mode 100644 index 0000000000000..8604054fa0824 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/manual-provision.md @@ -0,0 +1,7 @@ +--- +title: Manual provision setup +sidebar_position: 300 +unlisted: true +--- + +{/* TODO move content from https://docs.dagster.io/dagster-plus/deployment/agents/amazon-ecs/manually-provisioning-ecs-agent */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc.md new file mode 100644 index 0000000000000..d68622e6d7eb0 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc.md @@ -0,0 +1,7 @@ +--- +title: New VPC setup +sidebar_position: 100 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/amazon-ecs/creating-ecs-agent-new-vpc */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/upgrading-cloudformation.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/upgrading-cloudformation.md new file mode 100644 index 0000000000000..ee612a4ba34d4 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/upgrading-cloudformation.md @@ -0,0 +1,8 @@ +--- +title: Upgrading CloudFormation for an Amazon ECS agent +sidebar_label: Upgrading CloudFormation +sidebar_position: 500 +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/dagster-plus/deployment/agents/amazon-ecs/upgrading-cloudformation-template */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/architecture.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/architecture.md similarity index 96% rename from docs/docs-beta/docs/dagster-plus/deployment/hybrid/architecture.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/architecture.md index 3209f88f7a55d..7c21d41a38430 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/architecture.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/architecture.md @@ -1,11 +1,8 @@ --- title: 'Dagster+ Hybrid architecture' -displayed_sidebar: 'dagsterPlus' -sidebar_position: 100 +sidebar_position: 10 --- -# Dagster+ Hybrid architecture - The Hybrid architecture is the most flexible and secure way to deploy Dagster+. It allows you to run your user code in your environment while leveraging Dagster+'s infrastructure for orchestration and metadata management
@@ -83,7 +80,7 @@ Runs are launched by calling the `dagster api` CLI command in a separate process When runs are launched, the user code process/container streams structured metadata (containing everything that's viewable in the integrated logs viewer in the Dagster+ UI) back to Dagster+ over a well-defined GraphQL interface. Structured metadata is stored in Amazon RDS, encrypted at rest. -By default, the run worker also uploads the compute logs (raw `stdout` and `stderr` from runs) to Dagster+. If you don't want to upload logs, you can disable this feature in the [agent settings](/dagster-plus/deployment/hybrid/agents/settings). +By default, the run worker also uploads the compute logs (raw `stdout` and `stderr` from runs) to Dagster+. If you don't want to upload logs, you can disable this feature in the [agent settings](/dagster-plus/deployment/management/settings/hybrid-agent-settings). ### Ingress diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/configuration.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/configuration.md new file mode 100644 index 0000000000000..1294b30313cfb --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/configuration.md @@ -0,0 +1,7 @@ +--- +title: Docker agent configuration +sidebar_position: 200 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/docker/configuration-reference */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/migration/index.mdx b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/index.md similarity index 59% rename from docs/docs-beta/docs/dagster-plus/deployment/migration/index.mdx rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/index.md index 83ccdabe3b421..cb00c69f21296 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/migration/index.mdx +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/index.md @@ -1,11 +1,8 @@ --- -title: Migration -displayed_sidebar: "dagsterPlus" +title: Docker agent sidebar_position: 30 --- -# Migration - import DocCardList from '@theme/DocCardList'; \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/setup.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/setup.md new file mode 100644 index 0000000000000..f16e0dc8e25a9 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/docker/setup.md @@ -0,0 +1,7 @@ +--- +title: Docker agent setup +sidebar_position: 100 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/docker/configuring-running-docker-agent */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md similarity index 90% rename from docs/docs-beta/docs/dagster-plus/deployment/hybrid/index.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md index 5a7836ad79bcd..3d96293d0c923 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/index.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md @@ -1,11 +1,9 @@ --- title: "Hybrid deployment" -displayed_sidebar: "dagsterPlus" +sidebar_label: Hybrid sidebar_position: 20 --- -# Hybrid deployment - In a Dagster+ Hybrid deployment, the orchestration control plane is run by Dagster+ while your Dagster code is executed within your environment. [comment]: <> (TODO: Architecture diagram) @@ -23,10 +21,10 @@ To get started with a Hybrid deployment you'll need to: The Dagster+ agent is a long-lived process that polls Dagster+'s API servers for new work. See the following guides for setting up an agent: - - [Kubernetes](/dagster-plus/deployment/hybrid/agents/kubernetes) - - [AWS ECS](/dagster-plus/deployment/hybrid/agents/amazon-ecs-new-vpc) - - [Docker](/dagster-plus/deployment/hybrid/agents/docker) - - [Locally](/dagster-plus/deployment/hybrid/agents/local) + - [Kubernetes](/dagster-plus/deployment/deployment-types/hybrid/kubernetes) + - [AWS ECS](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc) + - [Docker](/dagster-plus/deployment/deployment-types/hybrid/docker) + - [Locally](/dagster-plus/deployment/deployment-types/hybrid/local) ## What you'll see in your environment diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/configuration.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/configuration.md new file mode 100644 index 0000000000000..f3053801d3c1c --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/configuration.md @@ -0,0 +1,7 @@ +--- +title: Kubernetes agent configuration +sidebar_position: 200 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/kubernetes/configuration-reference */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/index.md new file mode 100644 index 0000000000000..d744a447c3b87 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/index.md @@ -0,0 +1,8 @@ +--- +title: Kubernetes agent +sidebar_position: 40 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/kubernetes.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md similarity index 95% rename from docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/kubernetes.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md index 3c8612add3d87..619f5ffa72326 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/kubernetes.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md @@ -1,12 +1,8 @@ --- -title: "Running Dagster+ agents on Kubernetes" -displayed_sidebar: "dagsterPlus" -sidebar_position: 300 -sidebar_label: "Kubernetes" +title: Kubernetes agent setup +sidebar_position: 100 --- -# Running Dagster+ agents on Kubernetes - This page provides instructions for running the [Dagster+ agent](/todo) on a [Kubernetes](https://kubernetes.io) cluster. ## Installation @@ -28,7 +24,7 @@ kubectl create namespace dagster-cloud ### Step 2: Create an agent token secret -[Generate an agent token](/dagster-plus/deployment/hybrid/tokens) and set it as a Kubernetes secret: +[Generate an agent token](/dagster-plus/deployment/management/tokens) and set it as a Kubernetes secret: ```shell kubectl --namespace dagster-cloud create secret generic dagster-cloud-agent-token --from-literal=DAGSTER_CLOUD_AGENT_TOKEN= @@ -90,12 +86,12 @@ There are three places to customize how Dagster interacts with Kubernetes: Changes apply in a hierarchy, for example, a customization for an asset will override a default set globally in the agent configuration. Attributes that are not customized will use the global defaults. -An exhaustive list of settings is available [here](/dagster-plus/deployment/hybrid/agents/settings), but common options are presented below. +An exhaustive list of settings is available [here](/dagster-plus/deployment/management/settings/hybrid-agent-settings), but common options are presented below. ### Configure your agents to serve branch deployments -[Branch deployments](/dagster-plus/features/branch-deployments/index.mdx) are lightweight staging environments created for each code change. To configure your Dagster+ agent to manage them: +[Branch deployments](/dagster-plus/features/ci-cd/branch-deployments/index.md) are lightweight staging environments created for each code change. To configure your Dagster+ agent to manage them: ```yaml # values.yaml @@ -223,7 +219,7 @@ helm --namespace dagster-cloud upgrade agent \ ### Make secrets available to your code -You can make secrets available [through the Dagster+ web interface](/dagster-plus/deployment/environment-variables) or through Kubernetes. Configuring secrets through Kubernetes has the benefit that Dagster+ never stores or accesses the secrets, and they can be managed as code. First, create the Kubernetes secret: +You can make secrets available [through the Dagster+ web interface](/dagster-plus/deployment/management/environment-variables) or through Kubernetes. Configuring secrets through Kubernetes has the benefit that Dagster+ never stores or accesses the secrets, and they can be managed as code. First, create the Kubernetes secret: ```bash kubectl create secret generic database-password-kubernetes-secret \ diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/local.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/local.md similarity index 94% rename from docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/local.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/local.md index 2c3c48aa94460..53c43ba09d468 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/local.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/local.md @@ -1,11 +1,10 @@ --- -title: "Running a Dagster+ agent locally" -displayed_sidebar: "dagsterPlus" -sidebar_position: 600 -sidebar_label: "Local" +title: Running a local agent +sidebar_position: 20 +sidebar_label: Local agent --- -Local agents are a good way to experiment with Dagster+ before deploying a more scalable Hybrid agent like [Kubernetes](/dagster-plus/deployment/hybrid/agents/kubernetes) or [Amazon ECS](/todo). +Local agents are a good way to experiment with Dagster+ before deploying a more scalable Hybrid agent like [Kubernetes](/dagster-plus/deployment/deployment-types/hybrid/kubernetes) or [Amazon ECS](/todo). :::note Local agents aren't well suited for most production use cases. If you're running the local agent in production, make sure that: diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/multiple.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/multiple.md new file mode 100644 index 0000000000000..0df411c9e2b52 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/multiple.md @@ -0,0 +1,8 @@ +--- +title: Running multiple agents +sidebar_position: 60 +sidebar_label: Multiple agents +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/deployment/agents/running-multiple-agents */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/index.md new file mode 100644 index 0000000000000..bd70a65d90ffd --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/index.md @@ -0,0 +1,8 @@ +--- +title: Deployment types +sidebar_position: 20 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/multi-tenancy.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/multi-tenancy.md new file mode 100644 index 0000000000000..afac5b4cce012 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/multi-tenancy.md @@ -0,0 +1,5 @@ +--- +title: Multi-tenant +sidebar_position: 30 +unlisted: true +--- diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/ci-cd-in-serverless.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/ci-cd-in-serverless.md similarity index 81% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/ci-cd-in-serverless.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/ci-cd-in-serverless.md index e27b93194a034..265a378ea82b0 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/ci-cd-in-serverless.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/ci-cd-in-serverless.md @@ -1,17 +1,14 @@ --- -title: 'CI/CD in Serverless ' -displayed_sidebar: 'dagsterPlus' +title: 'CI/CD in Serverless' sidebar_position: 300 --- -# CI/CD in Serverless - -If you're a GitHub or GitLab user, you can use our predefined workflows to seamlessly deploy and synchronize your code to Dagster+. You can also use other Git providers or a local Git repository with our [dagster-cloud CLI](/dagster-plus/features/branch-deployments/dagster-cloud-cli) to run your own CI/CD process. +If you're a GitHub or GitLab user, you can use our predefined workflows to seamlessly deploy and synchronize your code to Dagster+. You can also use other Git providers or a local Git repository with our [dagster-cloud CLI](/dagster-plus/deployment/management/dagster-cloud-cli) to run your own CI/CD process. -If you're a GitHub user, with a single click our GitHub app with GitHub Actions can set up a repo containing skeleton code and configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/features/branch-deployments/index.mdx) that you can view in the Dagster+ UI for previewing and testing. +If you're a GitHub user, with a single click our GitHub app with GitHub Actions can set up a repo containing skeleton code and configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/features/ci-cd/branch-deployments/index.md) that you can view in the Dagster+ UI for previewing and testing. :::note **If you are importing a Dagster project that's in an existing GitHub repo:** @@ -28,13 +25,13 @@ If you're a GitHub user, with a single click our GitHub app with GitHub Actions -If you're a GitLab user, with a single click our GitLab app can set up a repo containing skeleton code and CI/CD configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/features/branch-deployments/index.mdx) that you can view in the Dagster+ UI for previewing and testing. +If you're a GitLab user, with a single click our GitLab app can set up a repo containing skeleton code and CI/CD configuration for you consistent with Dagster+'s best practices. Pushing your code changes to the `main` branch will automatically deploy them to your `prod` Serverless deployment. Pull requests will spin up ephemeral [branch deployments](/dagster-plus/features/ci-cd/branch-deployments/index.md) that you can view in the Dagster+ UI for previewing and testing. -If you don't want to use our automated GitHub/GitLab process, we offer [the powerful `dagster-cloud` command-line interface (CLI)](/dagster-plus/features/branch-deployments/dagster-cloud-cli) that you can use in another CI environment or locally. +If you don't want to use our automated GitHub/GitLab process, we offer [the powerful `dagster-cloud` command-line interface (CLI)](/dagster-plus/features/ci-cd/branch-deployments/dagster-cloud-cli) that you can use in another CI environment or locally. First, [create a new project](/getting-started/quickstart) with the Dagster open source CLI. @@ -62,7 +59,7 @@ install_requires=[ ::: -Next, install the [`dagster-cloud` CLI](/dagster-plus/features/branch-deployments/dagster-cloud-cli) and use its `configure` command to authenticate it to your Dagster+ organization. +Next, install the [`dagster-cloud` CLI](/dagster-plus/features/ci-cd/branch-deployments/dagster-cloud-cli) and use its `configure` command to authenticate it to your Dagster+ organization. **Note:** The CLI requires a recent version of Python 3 and Docker. @@ -71,7 +68,7 @@ pip install dagster-cloud dagster-cloud configure ``` -You can also configure the `dagster-cloud` tool non-interactively; see [the CLI docs](/dagster-plus/features/branch-deployments/dagster-cloud-cli) for more information. +You can also configure the `dagster-cloud` tool non-interactively; see [the CLI docs](/dagster-plus/features/ci-cd/branch-deployments/dagster-cloud-cli) for more information. Finally, deploy your project to Dagster+ using the `serverless` command: diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/dagster-ips.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/dagster-ips.md similarity index 84% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/dagster-ips.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/dagster-ips.md index 9b15bb595293e..2ea95704944f5 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/dagster-ips.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/dagster-ips.md @@ -1,11 +1,9 @@ --- -title: 'IP addresses' -displayed_sidebar: 'dagsterPlus' +title: Dagster+ Serverless IP addresses +sidebar_label: IP addresses sidebar_position: 400 --- -# Dagster+ Serverless IP addresses - Serverless code will make requests from one of the following IP addresses. You may need to whitelist / allowlist them for services your code interacts with. ```plain diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/index.md similarity index 95% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/index.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/index.md index 0684a378be624..02b9ce40ada82 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/index.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/index.md @@ -1,6 +1,6 @@ --- title: 'Serverless deployment' -displayed_sidebar: 'dagsterPlus' +sidebar_label: Serverless sidebar_position: 10 --- @@ -14,7 +14,7 @@ Dagster+ Serverless is a fully managed version of Dagster+ and is the easiest wa Serverless works best with workloads that primarily orchestrate other services or perform light computation. Most workloads fit into this category, especially those that orchestrate third-party SaaS products like cloud data warehouses and ETL tools. -If any of the following are applicable, you should select [Hybrid deployment](/dagster-plus/deployment/hybrid): +If any of the following are applicable, you should select [Hybrid deployment](/dagster-plus/deployment/deployment-types/hybrid): - You require substantial computational resources. For example, training a large machine learning (ML) model in-process - Your dataset is too large to fit in memory. For example, training a large ML model in-process on a terabyte of data diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/run-isolation.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/run-isolation.md similarity index 94% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/run-isolation.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/run-isolation.md index 68b58ee1231b5..c9c5d04ab6756 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/run-isolation.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/run-isolation.md @@ -1,12 +1,9 @@ --- title: 'Serverless run isolation' -displayed_sidebar: 'dagsterPlus' sidebar_label: 'Run isolation' sidebar_position: 200 --- -# Serverless run isolation - Dagster+ Serverless offers two settings for run isolation: isolated and non-isolated. Isolated runs are the default and are intended for production, while non-isolated runs are intended for faster iteration during development.
@@ -15,7 +12,7 @@ Dagster+ Serverless offers two settings for run isolation: isolated and non-isol To follow the steps in this guide, you'll need: - An active Dagster+ Serverless deployment -- An understanding of [Dagster+ deployment settings](/dagster-plus/deployment/deployment-settings) +- An understanding of [Dagster+ deployment settings](/dagster-plus/deployment/management/settings/deployment-settings)
--- @@ -57,7 +54,7 @@ While launching runs from the Launchpad, un-check `Isolate run environment`. Whe To avoid crashes and memory exhaustion, only one non-isolated run will execute at once by default. While a non-isolated run is in progress, the Launchpad will only allow isolated runs to be launched. -This limit can be configured in [deployment settings](/dagster-plus/deployment/deployment-settings). +This limit can be configured in [deployment settings](/dagster-plus/deployment/management/settings/deployment-settings). ```yaml non_isolated_runs: diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/runtime-environment.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/runtime-environment.md similarity index 85% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/runtime-environment.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/runtime-environment.md index 76cf15cb741db..750eefa59919a 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/runtime-environment.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/runtime-environment.md @@ -1,6 +1,5 @@ --- title: 'Serverless runtime environment' -displayed_sidebar: 'dagsterPlus' sidebar_label: 'Runtime environment' sidebar_position: 100 --- @@ -18,7 +17,7 @@ By default, Dagster+ Serverless will package your code as PEX files and deploys You can add dependencies by including the corresponding Python libraries in your Dagster project's `setup.py` file. These should follow [PEP 508](https://peps.python.org/pep-0508/). - + You can also use a tarball to install a dependency, such as if `pip` is unable to resolve a package using `dependency_links`. For example, `soda` and `soda-snowflake` provide tarballs that you can include in the `install_requires` section: @@ -49,18 +48,18 @@ The default Python version for Dagster+ Serverless is Python 3.9. Python version In your `.github/workflows/deploy.yml` file, update the `PYTHON_VERSION` environment variable with your desired Python version: - + 1. Open your `.gitlab-ci.yml` file. If your `.gitlab-ci.yml` contains an `include` with a link to a Dagster provided CI/CD template: - + Follow the link and replace the contents of your `.gitlab-ci.yml` with the YAML document at the link address. Otherwise, continue to the next step. 3. Update the `PYTHON_VERSION` environment variable with your desired Python version - + @@ -102,7 +101,7 @@ Setting a custom base image isn't supported for GitLab CI/CD workflows out of th In your `.github/workflows/deploy.yml` file, add the `SERVERLESS_BASE_IMAGE_TAG` environment variable and set it to the tag printed out in the previous step: - + @@ -133,7 +132,7 @@ To add data files to your deployment, use the [Data Files Support](https://setup ``` If you want to include the data folder, modify your `setup.py` to add the `package_data` line: - + ## Disable PEX deploys \{#disable-pex} @@ -142,18 +141,18 @@ You have the option to disable PEX-based deploys and deploy using a Docker image In your `.github/workflows/deploy.yml` file, update the `ENABLE_FAST_DEPLOYS` environment variable to `false`: - + 1. Open your `.gitlab-ci.yml` file. If your `.gitlab-ci.yml` contains an `include` with a link to a Dagster provided CI/CD template: - + Follow the link and replace the contents of your `.gitlab-ci.yml` with the YAML document at the link address. Otherwise, continue to the next step. 3. Update the `DISABLE_FAST_DEPLOYS` variable to `true` - + @@ -187,7 +186,7 @@ Setting a custom base image isn't supported for GitLab CI/CD workflows out of th In your `.github/workflows/deploy.yml` file, add the `SERVERLESS_BASE_IMAGE_TAG` environment variable and set it to the tag printed out in the previous step: - + diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/security.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/security.md similarity index 85% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/security.md rename to docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/security.md index d6a29601a7f44..bd1b23f2e1c6e 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/security.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/serverless/security.md @@ -1,12 +1,10 @@ --- -title: 'Security & data protection' -displayed_sidebar: 'dagsterPlus' +title: Serverless security & data protection +sidebar_label: 'Security & data protection' sidebar_position: 500 --- -# Serverless security & data protection - -Unlike [Hybrid deployments](/dagster-plus/deployment/hybrid), Serverless deployments on Dagster+ require direct access to your data, secrets and source code. +Unlike [Hybrid deployments](/dagster-plus/deployment/deployment-types/hybrid), Serverless deployments on Dagster+ require direct access to your data, secrets and source code. Secrets and source code are built into the image directly. Images are stored in a per-customer container registry with restricted access. User code is securely sandboxed using modern container sandboxing techniques. @@ -36,6 +34,6 @@ You must have [boto3](https://pypi.org/project/boto3/) or `dagster-cloud[serverl ## Adding environment variables and secrets \{#adding-secrets} -Often you'll need to securely access secrets from your jobs. Dagster+ supports several methods for adding secrets—refer to the [Dagster+ environment variables documentation](/dagster-plus/deployment/environment-variables) for more information. +Often you'll need to securely access secrets from your jobs. Dagster+ supports several methods for adding secrets—refer to the [Dagster+ environment variables documentation](/dagster-plus/deployment/management/environment-variables) for more information. --- diff --git a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/index.mdx b/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/index.mdx deleted file mode 100644 index 6184b57ef8d88..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/index.mdx +++ /dev/null @@ -1,12 +0,0 @@ ---- -title: "Environment variables" -displayed_sidebar: "dagsterPlus" -unlisted: true -sidebar_position: 40 ---- - -# Environment variables - -import DocCardList from '@theme/DocCardList'; - - diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/amazon-ecs-existing-vpc.md b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/amazon-ecs-existing-vpc.md deleted file mode 100644 index 24ce5ad107359..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/amazon-ecs-existing-vpc.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Amazon ECS agents (Existing VPC)" -displayed_sidebar: "dagsterPlus" -sidebar_position: 110 -sidebar_label: "Amazon ECS (Existing VPC)" -unlisted: true ---- diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/amazon-ecs-new-vpc.md b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/amazon-ecs-new-vpc.md deleted file mode 100644 index 8cfbd7c7b48b0..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/amazon-ecs-new-vpc.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Amazon ECS agents (New VPC)" -displayed_sidebar: "dagsterPlus" -sidebar_position: 100 -sidebar_label: "Amazon ECS (New VPC)" -unlisted: true ---- diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/docker.md b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/docker.md deleted file mode 100644 index ddd98a2f185a3..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/docker.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Docker agents" -displayed_sidebar: "dagsterPlus" -sidebar_position: 200 -sidebar_label: "Docker" -unlisted: true ---- - -# Docker agents diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/index.mdx b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/index.mdx deleted file mode 100644 index 2bd0168cc8167..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/index.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: "Agents" -displayed_sidebar: "dagsterPlus" -sidebar_class_name: hidden ---- - -# Agents - -import DocCardList from '@theme/DocCardList'; - - \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/multiple.md b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/multiple.md deleted file mode 100644 index 0ec8c793882cb..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/multiple.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Using multiple agents" -displayed_sidebar: "dagsterPlus" -sidebar_position: 400 -unlisted: true ---- - -# Use multiple agents with Dagster+ diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/settings.md b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/settings.md deleted file mode 100644 index 5fa76858ea8f7..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/agents/settings.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Hybrid agent settings" -displayed_sidebar: "dagsterPlus" -sidebar_position: 700 -sidebar_label: "Settings" -unlisted: true ---- - -# Hybrid agent settings diff --git a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/tokens.md b/docs/docs-beta/docs/dagster-plus/deployment/hybrid/tokens.md deleted file mode 100644 index 133556526e526..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/hybrid/tokens.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: 'Hybrid agent tokens' -displayed_sidebar: 'dagsterPlus' -sidebar_position: 200 -unlisted: true ---- - -# Hybrid agent tokens diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/dagster-cloud-cli-reference.md b/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/dagster-cloud-cli-reference.md new file mode 100644 index 0000000000000..90d74f2c112e5 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/dagster-cloud-cli-reference.md @@ -0,0 +1,7 @@ +--- +title: dagster-cloud CLI reference +sidebar_position: 200 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/managing-deployments/dagster-plus-cli#reference */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/index.md b/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/index.md new file mode 100644 index 0000000000000..96f6f0d097bd7 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/index.md @@ -0,0 +1,10 @@ +--- +title: dagster-cloud CLI +sidebar_position: 90 +--- + +The dagster-cloud CLI is a command-line toolkit designed to work with Dagster+. + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/installing-and-configuring.md b/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/installing-and-configuring.md new file mode 100644 index 0000000000000..ff5280c31f89c --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/dagster-cloud-cli/installing-and-configuring.md @@ -0,0 +1,8 @@ +--- +title: Installing and configuring the dagster-cloud CLI +sidebar_position: 100 +unlisted: true +--- + +{/* TODO copy from "Installing the CLI" and "Configuring the CLI" sections of https://docs.dagster.io/dagster-plus/managing-deployments/dagster-plus-cli */} + diff --git a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/agent-config.md b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/agent-config.md similarity index 54% rename from docs/docs-beta/docs/dagster-plus/deployment/environment-variables/agent-config.md rename to docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/agent-config.md index a22abdf31e07b..a800e113a83ba 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/agent-config.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/agent-config.md @@ -1,9 +1,8 @@ --- title: "Set environment variables using agent config" -displayed_sidebar: "dagsterPlus" sidebar_position: 300 sidebar_label: "Set with agent config" unlisted: true --- -# Set environment variables using agent config +{/* TODO move from https://docs.dagster.io/dagster-plus/managing-deployments/setting-environment-variables-agents */} diff --git a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/built-in.md b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/built-in.md similarity index 98% rename from docs/docs-beta/docs/dagster-plus/deployment/environment-variables/built-in.md rename to docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/built-in.md index 89eea22a2bef0..6bf5398f0088e 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/built-in.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/built-in.md @@ -1,11 +1,9 @@ --- title: "Built-in environment variables" -displayed_sidebar: "dagsterPlus" sidebar_position: 100 sidebar_label: "Built-in variables" --- - [Dagster+](/todo) provides a set of built-in, automatically populated environment variables, such as the name of a deployment or details about a branch deployment commit, that can be used to modify behavior based on environment. ### All deployment variables diff --git a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/dagster-ui.md b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/dagster-ui.md similarity index 95% rename from docs/docs-beta/docs/dagster-plus/deployment/environment-variables/dagster-ui.md rename to docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/dagster-ui.md index a4c76d4dba0b6..705aae2cba831 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/environment-variables/dagster-ui.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/dagster-ui.md @@ -1,6 +1,5 @@ --- title: "Setting environment variables with the Dagster+ UI" -displayed_sidebar: "dagsterPlus" sidebar_position: 200 sidebar_label: "Set with Dagster+ UI" --- @@ -90,4 +89,4 @@ For example, if you wanted to provide different Snowflake passwords for your pro ## Next steps - Learn how to [access environment variables in Dagster code](/todo) -- Learn about the [built-in environment variables](https://docs.dagster.io/dagster-plus/managing-deployments/environment-variables-and-secrets#built-in-environment-variables) provided by Dagster+ +- Learn about the [built-in environment variables](built-in) provided by Dagster+ diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/index.md b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/index.md new file mode 100644 index 0000000000000..59dace1b3724b --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/environment-variables/index.md @@ -0,0 +1,9 @@ +--- +title: Environment variables +sidebar_position: 60 +unlisted: true +--- + +import DocCardList from '@theme/DocCardList'; + + diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/index.mdx b/docs/docs-beta/docs/dagster-plus/deployment/management/index.md similarity index 53% rename from docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/index.mdx rename to docs/docs-beta/docs/dagster-plus/deployment/management/index.md index 19ee9983dc77d..144dd10871fe2 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/index.mdx +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/index.md @@ -1,11 +1,8 @@ --- -title: "SCIM provisioning" -displayed_sidebar: "dagsterPlus" +title: Deployment management sidebar_position: 30 --- -# SCIM provisioning - import DocCardList from '@theme/DocCardList'; \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/managing-compute-logs-and-error-messages.md b/docs/docs-beta/docs/dagster-plus/deployment/management/managing-compute-logs-and-error-messages.md new file mode 100644 index 0000000000000..01279273021f2 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/managing-compute-logs-and-error-messages.md @@ -0,0 +1,6 @@ +--- +title: Managing compute logs and error messages +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/dagster-plus/managing-deployments/controlling-logs */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/managing-multiple-projects-and-teams.md b/docs/docs-beta/docs/dagster-plus/deployment/management/managing-multiple-projects-and-teams.md new file mode 100644 index 0000000000000..cc59bd13364a9 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/managing-multiple-projects-and-teams.md @@ -0,0 +1,6 @@ +--- +title: Managing multiple projects and teams +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/dagster-plus/best-practices/managing-multiple-projects-and-teams */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md b/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md new file mode 100644 index 0000000000000..b4364e74ff276 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/rate-limits.md @@ -0,0 +1,6 @@ +--- +title: Dagster+ rate limits +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/dagster-plus/references/limits */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md new file mode 100644 index 0000000000000..df595ee48e153 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/customizing-agent-settings.md @@ -0,0 +1,7 @@ +--- +title: Customizing agent settings in dagster.yaml +sidebar_position: 80 +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/dagster-plus/deployment/agents/customizing-configuration */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/dagster-plus-settings.md b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/dagster-plus-settings.md similarity index 54% rename from docs/docs-beta/docs/dagster-plus/deployment/dagster-plus-settings.md rename to docs/docs-beta/docs/dagster-plus/deployment/management/settings/dagster-plus-settings.md index 0d7330cf5a6a9..ac4d6cfc1af70 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/dagster-plus-settings.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/dagster-plus-settings.md @@ -1,7 +1,6 @@ --- title: "Dagster+ settings" +sidebar_position: 100 unlisted: true -sidebar_position: 200 --- -# Dagster+ settings diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/settings/deployment-settings.md b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/deployment-settings.md new file mode 100644 index 0000000000000..c0cc4dbecca60 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/deployment-settings.md @@ -0,0 +1,7 @@ +--- +title: "Deployment settings" +sidebar_position: 200 +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/dagster-plus/managing-deployments/deployment-settings-reference */} diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/settings/hybrid-agent-settings.md b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/hybrid-agent-settings.md new file mode 100644 index 0000000000000..8b076b2f2e919 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/hybrid-agent-settings.md @@ -0,0 +1,8 @@ +--- +title: "Hybrid agent settings" +sidebar_position: 70 +unlisted: true +--- + +{/* TODO not sure why this page exists, is this covered by "Customizing agent settings"? */} + diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/settings/index.md b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/index.md new file mode 100644 index 0000000000000..0bc19ee72c5b6 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/settings/index.md @@ -0,0 +1,8 @@ +--- +title: Settings +sidebar_position: 70 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/agent-tokens.md b/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/agent-tokens.md new file mode 100644 index 0000000000000..e777a568a9f9f --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/agent-tokens.md @@ -0,0 +1,7 @@ +--- +title: 'Agent tokens' +sidebar_position: 200 +unlisted: true +--- + +{/* TODO move agent token content from https://docs.dagster.io/dagster-plus/account/managing-user-agent-tokens */} diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/index.md b/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/index.md new file mode 100644 index 0000000000000..f42a1600d7018 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/index.md @@ -0,0 +1,8 @@ +--- +title: Tokens +sidebar_position: 80 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/user-tokens.md b/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/user-tokens.md new file mode 100644 index 0000000000000..130e274d49ab7 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/management/tokens/user-tokens.md @@ -0,0 +1,7 @@ +--- +title: User tokens +sidebar_position: 100 +unlisted: true +--- + +{/* TODO move user token content from https://docs.dagster.io/dagster-plus/account/managing-user-agent-tokens */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/migration/index.md b/docs/docs-beta/docs/dagster-plus/deployment/migration/index.md new file mode 100644 index 0000000000000..ea7c4a344ade3 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/deployment/migration/index.md @@ -0,0 +1,8 @@ +--- +title: Migration +sidebar_position: 50 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/deployment/migration/self-hosted-to-dagster-plus.md b/docs/docs-beta/docs/dagster-plus/deployment/migration/self-hosted-to-dagster-plus.md index daee67878b339..e9ea6226a40ff 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/migration/self-hosted-to-dagster-plus.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/migration/self-hosted-to-dagster-plus.md @@ -1,5 +1,6 @@ --- -title: "Migrate from self-hosted to Dagster+" -sidebar_position: 100 +title: Migrating from self-hosted to Dagster+ +sidebar_label: Self-hosted to Dagster+ +sidebar_position: 200 unlisted: true --- diff --git a/docs/docs-beta/docs/dagster-plus/deployment/serverless/transition-hybrid.md b/docs/docs-beta/docs/dagster-plus/deployment/migration/serverless-to-hybrid.md similarity index 63% rename from docs/docs-beta/docs/dagster-plus/deployment/serverless/transition-hybrid.md rename to docs/docs-beta/docs/dagster-plus/deployment/migration/serverless-to-hybrid.md index 1ce8719fbde5e..f7b5d3e556fdd 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/serverless/transition-hybrid.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/migration/serverless-to-hybrid.md @@ -1,10 +1,10 @@ --- -title: "Transitioning to Hybrid" -displayed_sidebar: "dagsterPlus" -sidebar_position: 600 +title: Migrating from Serverless to Hybrid +sidebar_label: Serverless to Hybrid +sidebar_position: 100 --- -After utilizing a Dagster+ [Serverless](/dagster-plus/deployment/serverless) deployment, you may decide to leverage your own infrastructure to execute your code. Transitioning to a Hybrid deployment requires only a few steps and can be done without any loss of execution history or metadata, allowing you to maintain continuity and control over your operations. +After utilizing a Dagster+ [Serverless](/dagster-plus/deployment/deployment-types/serverless) deployment, you may decide to leverage your own infrastructure to execute your code. Transitioning to a Hybrid deployment requires only a few steps and can be done without any loss of execution history or metadata, allowing you to maintain continuity and control over your operations. :::warning Transitioning from Serverless to Hybrid requires some downtime, as your Dagster+ deployment won't have an agent to execute user code. @@ -33,9 +33,9 @@ It may take a few minutes for the agent to deactivate and be removed from the li Next, you'll need to create a Hybrid agent to execute your code. Follow the setup instructions for the agent of your choice: - **[Amazon Web Services (AWS)](/todo)**, which launches user code as Amazon Elastic Container Service (ECS) tasks. -- **[Docker](/dagster-plus/deployment/hybrid/agents/docker)**, which launches user code in Docker containers on your machine -- **[Kubernetes](/dagster-plus/deployment/hybrid/agents/kubernetes)**, which launches user code on a Kubernetes cluster -- **[Local](/dagster-plus/deployment/hybrid/agents/local)**, which launches user code in operating system subprocesses on your machine +- **[Docker](/dagster-plus/deployment/deployment-types/hybrid/docker)**, which launches user code in Docker containers on your machine +- **[Kubernetes](/dagster-plus/deployment/deployment-types/hybrid/kubernetes)**, which launches user code on a Kubernetes cluster +- **[Local](/dagster-plus/deployment/deployment-types/hybrid/local)**, which launches user code in operating system subprocesses on your machine ## Step 3: Confirm successful setup diff --git a/docs/docs-beta/docs/dagster-plus/deployment/multi-tenancy.md b/docs/docs-beta/docs/dagster-plus/deployment/multi-tenancy.md deleted file mode 100644 index 28b41d6d7f9d3..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/multi-tenancy.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Multi-tenancy" -unlisted: true -sidebar_position: 500 ---- - -# Dagster+ multi-tenancy diff --git a/docs/docs-beta/docs/dagster-plus/deployment/user-agent-tokens.md b/docs/docs-beta/docs/dagster-plus/deployment/user-agent-tokens.md deleted file mode 100644 index 8a1b94d891046..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/deployment/user-agent-tokens.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Tokens" -displayed_sidebar: "dagsterPlus" -unlisted: true -sidebar_position: 600 ---- - -# Managing user and agent tokens in Dagster+ diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/cli.md b/docs/docs-beta/docs/dagster-plus/features/alerts/cli.md deleted file mode 100644 index 71e28ce328c5e..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/cli.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Dagster+ alerts with the CLI" -unlisted: true -sidebar_position: 200 ---- - -# Alerts with the CLI diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/configuring-an-alert-notification-service.md b/docs/docs-beta/docs/dagster-plus/features/alerts/configuring-an-alert-notification-service.md new file mode 100644 index 0000000000000..5cd722b49385b --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/alerts/configuring-an-alert-notification-service.md @@ -0,0 +1,52 @@ +--- +title: Configuring an alert notification service +sidebar_position: 100 +--- + +Dagster+ allows you to configure alerts to fire in response to a range of events. These alerts can be sent to a variety of different services, depending on your organization's needs. + +{/* TODO this needs content on the value prop of alerts -- save money, etc */} + +:::note +You must have **Organization**, **Admin**, or **Editor** permissions on Dagster+ to configure an alert notification service. +::: + +Before [creating alerts](creating-alerts), you'll need to configure a service to send alerts. Dagster+ currently supports sending alerts through email, Microsoft Teams, PagerDuty, and Slack. + + + + No additional configuration is required to send emails from Dagster+. + +All alert emails will be sent by `"no-reply@dagster.cloud"` or `"no-reply@.dagster.cloud"`. Alerts can be configured to be sent to any number of emails. + + + Create an incoming webhook by following the [Microsoft Teams documentation](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet). + +This will provide you with a **webhook URL** which will be required when configuring alerts in the UI (after selecting "Microsoft Teams" as your Notification Service) or using the CLI (in the `notification_service` configuration). + + + + :::note +You will need sufficient permissions in PagerDuty to add or edit services. +::: + +In PagerDuty, you can either: + +- [Create a new service](https://support.pagerduty.com/main/docs/services-and-integrations#create-a-service), and add Dagster+ as an integration, or +- [Edit an existing service](https://support.pagerduty.com/main/docs/services-and-integrations#edit-service-settings) to include Dagster+ as an integration + +When configuring the integration, choose **Dagster+** as the integration type, and choose an integration name in the format `dagster-plus-{your_service_name}`. + +After adding your new integration, you will be taken to a screen containing an **Integration Key**. This value will be required when configuring alerts in the UI (after selecting "PagerDuty" as your Notification Service) or using the CLI (in the `notification_service` configuration). + + + + :::note +You will need sufficient permissions in Slack to add apps to your workspace. +::: +Navigate to **Deployment > Alerts** in the Dagster+ UI and click **Connect to Slack**. From there, you can complete the installation process. + +When setting up an alert, you can choose a Slack channel to send those alerts to. Make sure to invite the `@Dagster+` bot to any channel that you'd like to receive an alert in. + + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/creating-alerts.md b/docs/docs-beta/docs/dagster-plus/features/alerts/creating-alerts.md new file mode 100644 index 0000000000000..8239359b605fd --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/alerts/creating-alerts.md @@ -0,0 +1,277 @@ +--- +title: Creating alerts in Dagster+ +sidebar_position: 200 +--- + +You can create alerts in the Dagster+ UI or using the [`dagster-cloud` CLI](/dagster-plus/deployment/management/dagster-cloud-cli). + +{/* TODO link to dagster-cloud CLI tool doc */} + +:::note +Before you create alerts, you must [configure an alert notification service](configuring-an-alert-notification-service). +::: + +## Alerting when a run fails +You can set up alerts to notify you when a run fails. + +By default, these alerts will target all runs in the deployment, but they can be scoped to runs with a specific tag. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Run alert** from the dropdown. + +5. Select **Job failure**. + +If desired, add **tags** in the format `{key}:{value}` to filter the runs that will be considered. + + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + + +## Alerting when a run is taking too long to complete +You can set up alerts to notify you whenever a run takes more than some threshold amount of time. + + By default, these alerts will target all runs in the deployment, but they can be scoped to runs with a specific tag. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Run alert** from the dropdown. + +5. Select **Job running over** and how many hours to alert after. + +If desired, add **tags** in the format `{key}:{value}` to filter the runs that will be considered. + + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + + +## Alerting when an asset fails to materialize +You can set up alerts to notify you when an asset materialization attempt fails. + +By default, these alerts will target all assets in the deployment, but they can be scoped to a specific asset or group of assets. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Asset alert** from the dropdown. + +5. Select **Failure** under the **Materializations** heading. + +If desired, select a **target** from the dropdown menu to scope this alert to a specific asset or group. + + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + + +## Alerting when an asset check fails +You can set up alerts to notify you when an asset check on an asset fails. + +By default, these alerts will target all assets in the deployment, but they can be scoped to checks on a specific asset or group of assets. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Asset alert** from the dropdown. + +5. Select **Failed (ERROR)** under the **Asset Checks** heading. + +If desired, select a **target** from the dropdown menu to scope this alert to a specific asset or group. + + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + + +## Alerting when a schedule or sensor tick fails +You can set up alerts to fire when any schedule or sensor tick across your entire deployment fails. + +Alerts are sent only when a schedule/sensor transitions from **success** to **failure**, so only the initial failure will trigger the alert. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Schedule/Sensor alert** from the dropdown. + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + + +## Alerting when a code location fails to load +You can set up alerts to fire when any code location fails to load due to an error. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Code location error alert** from the dropdown. + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + + +## Alerting when a Hybrid agent becomes unavailable +:::note +This is only available for [Hybrid](/todo) deployments. +::: + +You can set up alerts to fire if your Hybrid agent hasn't sent a heartbeat in the last 5 minutes. + + + 1. In the Dagster UI, click **Deployment**. +2. Click the **Alerts** tab. +3. Click **Add alert policy**. +4. Select **Code location error alert** from the dropdown. + + + Execute the following command to sync the configured alert policy to your Dagster+ deployment. + + ```bash + dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml + ``` + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/email.md b/docs/docs-beta/docs/dagster-plus/features/alerts/email.md deleted file mode 100644 index 2b516c6b73bac..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/email.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Dagster+ email alerts" -unlisted: true -sidebar_position: 300 ---- - -# Dagster+ email alerts diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/index.md b/docs/docs-beta/docs/dagster-plus/features/alerts/index.md index b869009c354d0..fcdb9c9068ac1 100644 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/index.md +++ b/docs/docs-beta/docs/dagster-plus/features/alerts/index.md @@ -1,322 +1,8 @@ --- -title: Setting up alerts on Dagster+ -sidebar_label: "Dagster+ Alerts" -sidebar_position: 30 +title: Alerts +sidebar_position: 40 --- -[comment]: <> (This file is automatically generated by `dagster-plus/deployment/alerts/generate_alerts_doc.py`) -Dagster+ allows you to configure alerts to automatically fire in response to a range of events. These alerts can be sent to a variety of different services, depending on your organization's needs. +import DocCardList from '@theme/DocCardList'; -These alerts can be configured in the Dagster+ UI, or using the `dagster-cloud` CLI tool. - -
-Prerequisites -- **Organization**, **Admin**, or **Editor** permissions on Dagster+ -
- -## Configuring a notification service - -To start, you'll need to configure a service to send alerts. Dagster+ current supports sending alerts through email, Microsoft Teams, PagerDuty, and Slack. - - - - No additional configuration is required to send emails from Dagster+. - -All alert emails will be sent by `"no-reply@dagster.cloud"` or `"no-reply@.dagster.cloud"`. Alerts can be configured to be sent to any number of emails. - - - Create an incoming webhook by following the [Microsoft Teams documentation](https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet). - -This will provide you with a **webhook URL** which will be required when configuring alerts in the UI (after selecting "Microsoft Teams" as your Notification Service) or using the CLI (in the `notification_service` configuration). - - - - :::note -You will need sufficient permissions in PagerDuty to add or edit services. -::: - -In PagerDuty, you can either: - -- [Create a new service](https://support.pagerduty.com/main/docs/services-and-integrations#create-a-service), and add Dagster+ as an integration, or -- [Edit an existing service](https://support.pagerduty.com/main/docs/services-and-integrations#edit-service-settings) to include Dagster+ as an integration - -When configuring the integration, choose **Dagster+** as the integration type, and choose an integration name in the format `dagster-plus-{your_service_name}`. - -After adding your new integration, you will be taken to a screen containing an **Integration Key**. This value will be required when configuring alerts in the UI (after selecting "PagerDuty" as your Notification Service) or using the CLI (in the `notification_service` configuration). - - - - :::note -You will need sufficient permissions in Slack to add apps to your workspace. -::: -Navigate to **Deployment > Alerts** in the Dagster+ UI and click **Connect to Slack**. From there, you can complete the installation process. - -When setting up an alert, you can choose a Slack channel to send those alerts to. Make sure to invite the `@Dagster+` bot to any channel that you'd like to receive an alert in. - - - - -## Alerting when a run fails -You can set up alerts to notify you when a run fails. - -By default, these alerts will target all runs in the deployment, but they can be scoped to runs with a specific tag. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Run alert** from the dropdown. - -5. Select **Job failure**. - -If desired, add **tags** in the format `{key}:{value}` to filter the runs that will be considered. - - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - - -## Alerting when a run is taking too long to complete -You can set up alerts to notify you whenever a run takes more than some threshold amount of time. - - By default, these alerts will target all runs in the deployment, but they can be scoped to runs with a specific tag. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Run alert** from the dropdown. - -5. Select **Job running over** and how many hours to alert after. - -If desired, add **tags** in the format `{key}:{value}` to filter the runs that will be considered. - - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - - -## Alerting when an asset fails to materialize -You can set up alerts to notify you when an asset materialization attempt fails. - -By default, these alerts will target all assets in the deployment, but they can be scoped to a specific asset or group of assets. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Asset alert** from the dropdown. - -5. Select **Failure** under the **Materializations** heading. - -If desired, select a **target** from the dropdown menu to scope this alert to a specific asset or group. - - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - - -## Alerting when an asset check fails -You can set up alerts to notify you when an asset check on an asset fails. - -By default, these alerts will target all assets in the deployment, but they can be scoped to checks on a specific asset or group of assets. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Asset alert** from the dropdown. - -5. Select **Failed (ERROR)** under the **Asset Checks** heading. - -If desired, select a **target** from the dropdown menu to scope this alert to a specific asset or group. - - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - - -## Alerting when a schedule or sensor tick fails -You can set up alerts to fire when any schedule or sensor tick across your entire deployment fails. - -Alerts are sent only when a schedule/sensor transitions from **success** to **failure**, so only the initial failure will trigger the alert. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Schedule/Sensor alert** from the dropdown. - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - - -## Alerting when a code location fails to load -You can set up alerts to fire when any code location fails to load due to an error. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Code location error alert** from the dropdown. - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - - -## Alerting when a Hybrid agent becomes unavailable -:::note -This is only available for [Hybrid](/todo) deployments. -::: - -You can set up alerts to fire if your Hybrid agent hasn't sent a heartbeat in the last 5 minutes. - - - 1. In the Dagster UI, click **Deployment**. -2. Click the **Alerts** tab. -3. Click **Add alert policy**. -4. Select **Code location error alert** from the dropdown. - - - Execute the following command to sync the configured alert policy to your Dagster+ deployment. - - ```bash - dagster-cloud deployment alert-policies sync -a /path/to/alert_policies.yaml - ``` - - - - - - - - - - - - - - - - - \ No newline at end of file + diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/microsoft-teams.md b/docs/docs-beta/docs/dagster-plus/features/alerts/microsoft-teams.md deleted file mode 100644 index 7c66b3e2dae8b..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/microsoft-teams.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Dagster+ Microsoft Teams alerts" -unlisted: true -sidebar_label: "Microsoft Teams" -sidebar_position: 400 ---- - -# Dagster+ Microsoft Teams alerts diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/pagerduty.md b/docs/docs-beta/docs/dagster-plus/features/alerts/pagerduty.md deleted file mode 100644 index c8a32645e592f..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/pagerduty.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Dagster+ PagerDuty alerts" -unlisted: true -sidebar_label: "PagerDuty" -sidebar_position: 500 ---- - -# Dagster+ PagerDuty alerts diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/slack.md b/docs/docs-beta/docs/dagster-plus/features/alerts/slack.md deleted file mode 100644 index 3d9f5423dd890..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/slack.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Dagster+ Slack alerts" -unlisted: true -sidebar_label: "Slack" -sidebar_position: 600 ---- - -# Dagster+ Slack alerts diff --git a/docs/docs-beta/docs/dagster-plus/features/alerts/ui.md b/docs/docs-beta/docs/dagster-plus/features/alerts/ui.md deleted file mode 100644 index b613282af846e..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/alerts/ui.md +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "Dagster+ alerts in the UI" -unlisted: true -sidebar_label: "UI" -sidebar_position: 100 ---- - -# Alerts in the UI diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/index.mdx b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/index.md similarity index 55% rename from docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/index.mdx rename to docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/index.md index a17a4992483d4..4b3a0e15bfa4f 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/index.mdx +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/index.md @@ -1,11 +1,8 @@ --- title: "Authentication and access control" -displayed_sidebar: "dagsterPlus" -sidebar_position: 40 +sidebar_position: 10 --- -# Authentication and access control - import DocCardList from '@theme/DocCardList'; \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/audit-logs.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/audit-logs.md index cfc6c1cd81337..fd298db800102 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/audit-logs.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/audit-logs.md @@ -1,11 +1,8 @@ --- title: "Audit logs" -displayed_sidebar: "dagsterPlus" sidebar_position: 300 --- -# Audit logs - The Dagster+ audit log enables Dagster+ Pro organizations to track and attribute changes to their Dagster deployment. For large organizations, tracking down when and by whom changes were made can be crucial for maintaining security and compliance. The audit log is also valuable @@ -46,7 +43,7 @@ The **Filter** button near the top left of the page can be used to filter the li | Log in | A user logs in to the Dagster+ organization | | | Update sensor | A user toggles a sensor on or off | The sensor name, code location, and cursor | | Update schedule | A user toggles a schedule on or off | The schedule name, code location, and cursor | -| Update alert policy | A user modifies an [alert policy](/dagster-plus/features/alerts/ui) | The new configuration for the alert policy | +| Update alert policy | A user modifies an [alert policy](/dagster-plus/features/alerts/creating-alerts) | The new configuration for the alert policy | | Create deployment | A user creates a new deployment | Whether the deployment is a branch deployment | | Delete deployment | A user removes an existing deployment | Whether the deployment is a branch deployment | | Create user token | A user creates a new user token | | @@ -55,9 +52,9 @@ The **Filter** button near the top left of the page can be used to filter the li | Create agent token | A user creates a new agent token | | | Revoke agent token | A user revokes an existing agent token | | | Update agent token permissions | A user alters [permissions](/dagster-plus/features/authentication-and-access-control/rbac/user-roles-permissions) for an agent token | The permission grant and targeted deployment | -| Create secret | A user creates a new [environment variable](/dagster-plus/deployment/environment-variables/dagster-ui) | The created variable name | -| Update secret | A user modifies an existing [environment variable](/dagster-plus/deployment/environment-variables/dagster-ui) | The previous and current variable names and whether the value was changed | -| Delete secret | A user removes an [environment variable](/dagster-plus/deployment/environment-variables/dagster-ui) | The deleted variable name | +| Create secret | A user creates a new [environment variable](/dagster-plus/deployment/management/environment-variables/dagster-ui) | The created variable name | +| Update secret | A user modifies an existing [environment variable](/dagster-plus/deployment/management/environment-variables/dagster-ui) | The previous and current variable names and whether the value was changed | +| Delete secret | A user removes an [environment variable](/dagster-plus/deployment/management/environment-variables/dagster-ui) | The deleted variable name | | Update subscription | A user modifies the selected Dagster+ subscription for the organization | The previous and current plan types | ## Programmatic access to audit logs diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/index.mdx b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/index.md similarity index 67% rename from docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/index.mdx rename to docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/index.md index 1443bd749b3b4..5f6a44b46616a 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/index.mdx +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/index.md @@ -1,11 +1,8 @@ --- title: "Role-based access control" -displayed_sidebar: "dagsterPlus" sidebar_position: 10 --- -# Role-based access control - import DocCardList from '@theme/DocCardList'; \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/teams.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/teams.md index dff5866950069..894a4a29f0db9 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/teams.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/teams.md @@ -1,11 +1,9 @@ --- -title: "Team management" -displayed_sidebar: "dagsterPlus" +title: Team management in Dagster+ +sidebar_label: "Team management" sidebar_position: 100 --- -# Team management in Dagster+ - As part of [role-based access control (RBAC)](/dagster-plus/features/authentication-and-access-control/rbac/user-roles-permissions), Dagster+ supports the ability to assign users to teams. A team is a group of users with a set of default deployment, code location, and Branch Deployment user roles.
diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/user-roles-permissions.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/user-roles-permissions.md index 6281ae236cd9e..d6ce4c96de5e3 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/user-roles-permissions.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/user-roles-permissions.md @@ -1,11 +1,9 @@ --- -title: 'User roles & permissions' -displayed_sidebar: 'dagsterPlus' +title: User roles & permissions in Dagster+ +sidebar_label: 'User roles & permissions' sidebar_position: 200 --- -# Understanding user roles & permissions in Dagster+ - Role-based access control (RBAC) enables you to grant specific permissions to users in your organization, ensuring that Dagster users have access to what they require in Dagster+, and no more. In this guide, we'll cover how RBAC works in Dagster+, how to assign roles to users, and the granular permissions for each user role. @@ -44,7 +42,7 @@ Dagster+ Pro users can create teams of users and assign default permission sets. With the exception of the **Organization Admin** role, user and team roles are set on a per-deployment basis. -Organization Admins have access to the entire organization, including all [deployments](/todo), [code locations](/dagster-plus/deployment/code-locations), and [Branch Deployments](dagster-plus/features/branch-deployments/index.mdx). +Organization Admins have access to the entire organization, including all [deployments](/todo), [code locations](/dagster-plus/deployment/code-locations), and [Branch Deployments](dagster-plus/features/ci-cd/branch-deployments/index.md). | Level | Plan | Description | | ------------------ | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -128,11 +126,11 @@ Deployment settings are accessed in the UI by navigating to **user menu (your ic |----------------------------------------------------------------------------------------------|-------|-----------|--------|-------|-------------------------------| | View [deployments](/todo) | ✅ | ✅ | ✅ | ✅ | ✅ | | Modify [deployment](/todo) settings | ❌ | ❌ | ✅ | ✅ | ✅ | -| Create, edit, delete [environment variables](/dagster-plus/deployment/environment-variables) | ❌ | ❌ | ✅ | ✅ | ✅ | -| View [environment variable](/dagster-plus/deployment/environment-variables) values | ❌ | ❌ | ✅ | ✅ | ✅ | -| Export [environment variables](/dagster-plus/deployment/environment-variables) | ❌ | ❌ | ✅ | ✅ | ✅ | +| Create, edit, delete [environment variables](/dagster-plus/deployment/management/environment-variables) | ❌ | ❌ | ✅ | ✅ | ✅ | +| View [environment variable](/dagster-plus/deployment/management/environment-variables) values | ❌ | ❌ | ✅ | ✅ | ✅ | +| Export [environment variables](/dagster-plus/deployment/management/environment-variables) | ❌ | ❌ | ✅ | ✅ | ✅ | | Create and delete [deployments](/todo) | ❌ | ❌ | ❌ | ❌ | ✅ | -| Create [Branch Deployments](dagster-plus/features/branch-deployments/index.mdx) | ❌ | ❌ | ✅ | ✅ | ✅ | +| Create [Branch Deployments](dagster-plus/features/ci-cd/branch-deployments/index.md) | ❌ | ❌ | ✅ | ✅ | ✅ | ### Code locations @@ -150,7 +148,7 @@ Agent tokens are accessed in the UI by navigating to **user menu (your icon) > O | | Viewer | Launcher | Editor | Admin | Organization
admin | | ----------------------------------------------------------- | ------ | -------- | ------ | ----- | ------------------------ | -| View [agent tokens](/dagster-plus/deployment/hybrid/tokens) | ❌ | ❌ | ❌ | ❌ | ✅ | +| View [agent tokens](/dagster-plus/deployment/management/tokens/agent-tokens) | ❌ | ❌ | ❌ | ❌ | ✅ | | Create agent tokens | ❌ | ❌ | ❌ | ❌ | ✅ | | Edit agent tokens | ❌ | ❌ | ❌ | ❌ | ✅ | | Revoke agent tokens | ❌ | ❌ | ❌ | ❌ | ✅ | @@ -207,5 +205,5 @@ Team management is accessed in the UI by navigating to **user menu (your icon) > - Learn more about how to manage users in Dagster+ in [Understanding User Management in Dagster+](/dagster-plus/features/authentication-and-access-control/rbac/users) - Learn more about how to manage teams in Dagster+ in [Understanding Team Management in Dagster+](/dagster-plus/features/authentication-and-access-control/rbac/teams) -- Learn more about SCIM provisioning in [Understanding SCIM Provisioning](/dagster-plus/features/authentication-and-access-control/scim/index.mdx) +- Learn more about SCIM provisioning in [Understanding SCIM Provisioning](/dagster-plus/features/authentication-and-access-control/scim/index.md) - Learn more about authentication in [Understanding Authentication](/dagster-plus/features/authentication-and-access-control/sso/authentication) diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/users.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/users.md index 61c3a2f55401f..2f1294cb4fb17 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/users.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/rbac/users.md @@ -1,6 +1,5 @@ --- title: "Managing users in Dagster+" -displayed_sidebar: "dagsterPlus" sidebar_label: "User management" sidebar_position: 400 --- diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/azure-active-directory.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/azure-active-directory.md index 28fd1473a5e56..a27c033a49b64 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/azure-active-directory.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/azure-active-directory.md @@ -1,10 +1,6 @@ --- title: 'Azure Active Directory' -displayed_sidebar: 'dagsterPlus' -unlisted: true -sidebar_position: 200 +sidebar_position: 300 --- -# Azure Active Directory - -See the [Dagster Cloud provisioning tutorial](https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/dagster-cloud-provisioning-tutorial). +See the [Microsoft Dagster Cloud provisioning tutorial](https://learn.microsoft.com/en-us/azure/active-directory/saas-apps/dagster-cloud-provisioning-tutorial). diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/enabling-scim-provisioning.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/enabling-scim-provisioning.md new file mode 100644 index 0000000000000..2effe2befed3a --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/enabling-scim-provisioning.md @@ -0,0 +1,7 @@ +--- +title: Enabling SCIM provisioning +sidebar_position: 100 +unlisted: true +--- + +{/* TODO content from https://docs.dagster.io/dagster-plus/account/authentication/utilizing-scim-provisioning#enabling-scim-provisioning should be copied here */} diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/index.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/index.md new file mode 100644 index 0000000000000..392c7b0be278a --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/index.md @@ -0,0 +1,11 @@ +--- +title: "SCIM provisioning" +sidebar_position: 30 +unlisted: true +--- + +{/* TODO content from top of "Utilizing SCIM provisioning" https://docs.dagster.io/dagster-plus/account/authentication/utilizing-scim-provisioning page and "Understanding SCIM provisioning" section https://docs.dagster.io/dagster-plus/account/authentication/utilizing-scim-provisioning#understanding-scim-provisioning should be copied here. */} + +## User management with SCIM + +## Team management with SCIM \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/okta-scim.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/okta-scim.md index a1dd29b1bf275..c007683bc3df8 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/okta-scim.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/scim/okta-scim.md @@ -1,8 +1,7 @@ --- title: 'Okta SCIM provisioning' -displayed_sidebar: 'dagsterPlus' +sidebar_position: 200 unlisted: true -sidebar_position: 100 --- -# Okta SCIM provisioning +{/* TODO copy from https://docs.dagster.io/dagster-plus/account/authentication/okta/scim-provisioning */} diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/authentication.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/authentication.md index 2c626adac16d8..4a3489acf0fbe 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/authentication.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/authentication.md @@ -1,8 +1,6 @@ --- title: "Authentication" -displayed_sidebar: "dagsterPlus" -unlisted: true sidebar_position: 100 +unlisted: true --- -# Authentication diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/azure-ad-sso.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/azure-ad-sso.md index 5921d30d4d995..969014b7520cd 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/azure-ad-sso.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/azure-ad-sso.md @@ -1,11 +1,9 @@ --- -title: 'Azure Active Directory SSO' -displayed_sidebar: 'dagsterPlus' +title: Setting up Azure Active Directory SSO for Dagster+ +sidebar_label: 'Azure Active Directory SSO' sidebar_position: 200 --- -# Setting up Azure Active Directory SSO for Dagster+ - In this guide, you'll configure Azure Active Directory (AD) to use single sign-on (SSO) with your Dagster+ organization.
diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/google-workspace-sso.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/google-workspace-sso.md index 49727f24ad5c2..6c980a33717f7 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/google-workspace-sso.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/google-workspace-sso.md @@ -1,11 +1,9 @@ --- -title: 'Google Workspace SSO' -displayed_sidebar: 'dagsterPlus' +title: Setting up Google Workspace SSO for Dagster+ +sidebar_label: 'Google Workspace SSO' sidebar_position: 300 --- -# Setting up Google Workspace SSO for Dagster+ - In this guide, you'll configure Google Workspace to use single sign-on (SSO) with your Dagster+ organization.
diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/index.mdx b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/index.md similarity index 69% rename from docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/index.mdx rename to docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/index.md index fe5219e36a95f..e5711aad31dd8 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/index.mdx +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/index.md @@ -1,11 +1,8 @@ --- title: "Single sign-on" -displayed_sidebar: "dagsterPlus" sidebar_position: 20 --- -# Single sign-on - import DocCardList from '@theme/DocCardList'; \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/okta-sso.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/okta-sso.md index 2b9d01f0aeda1..7161afbccd1cb 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/okta-sso.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/okta-sso.md @@ -1,11 +1,9 @@ --- -title: 'Okta SSO' -displayed_sidebar: 'dagsterPlus' +title: Setting up Okta SSO for Dagster+ +sidebar_label: 'Okta SSO' sidebar_position: 400 --- -# Setting up Okta SSO for Dagster+ - In this guide, you'll configure Okta to use single sign-on (SSO) with your Dagster+ organization.
diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/onelogin-sso.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/onelogin-sso.md index 4b9c10a57c1a7..5c4ec8a246dda 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/onelogin-sso.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/onelogin-sso.md @@ -1,11 +1,8 @@ --- title: 'OneLogin SSO' -displayed_sidebar: 'dagsterPlus' sidebar_position: 500 --- -# OneLogin SSO - In this guide, you'll configure OneLogin to use single sign-on (SSO) with your Dagster+ organization. diff --git a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/pingone-sso.md b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/pingone-sso.md index 2c766cb1cfc70..3b824c9c5c24d 100644 --- a/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/pingone-sso.md +++ b/docs/docs-beta/docs/dagster-plus/features/authentication-and-access-control/sso/pingone-sso.md @@ -1,11 +1,9 @@ --- -title: 'PingOne SSO' -displayed_sidebar: 'dagsterPlus' +title: Setting up PingOne SSO for Dagster+ +sidebar_label: 'PingOne SSO' sidebar_position: 600 --- -# Setting up PingOne SSO for Dagster+ - In this guide, you'll configure PingOne to use single sign-on (SSO) with your Dagster+ organization.
diff --git a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/change-tracking.md b/docs/docs-beta/docs/dagster-plus/features/branch-deployments/change-tracking.md deleted file mode 100644 index 40b5a837ae8d6..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/change-tracking.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Change tracking in branch deployments" -displayed_sidebar: "dagsterPlus" -sidebar_position: 200 -sidebar_label: "Change tracking" -unlisted: true ---- - -# Change tracking in branch deployments diff --git a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/dagster-cloud-cli.md b/docs/docs-beta/docs/dagster-plus/features/branch-deployments/dagster-cloud-cli.md deleted file mode 100644 index 76615d4e4ad5d..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/dagster-cloud-cli.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -title: "Branch deployments & the dagster-cloud CLI" -displayed_sidebar: "dagsterPlus" -sidebar_position: 300 -sidebar_label: "dagster-cloud CLI" -unlisted: true ---- - -# Use branch deployments with the dagster-cloud CLI diff --git a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/index.mdx b/docs/docs-beta/docs/dagster-plus/features/branch-deployments/index.mdx deleted file mode 100644 index bdb1ae1d19be9..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/index.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: "Branch deployments (CI)" -displayed_sidebar: "dagsterPlus" -sidebar_position: 20 ---- - -# Branch deployments (CI) - -import DocCardList from '@theme/DocCardList'; - - \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/testing.md b/docs/docs-beta/docs/dagster-plus/features/branch-deployments/testing.md deleted file mode 100644 index aaf141806d021..0000000000000 --- a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/testing.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Testing against production with branch deployments" -unlisted: true -sidebar_position: 400 ---- - -# Testing against production with branch deployments \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/saved-views.md b/docs/docs-beta/docs/dagster-plus/features/catalog-views.md similarity index 91% rename from docs/docs-beta/docs/dagster-plus/features/saved-views.md rename to docs/docs-beta/docs/dagster-plus/features/catalog-views.md index fc06f04032485..201467bd939ad 100644 --- a/docs/docs-beta/docs/dagster-plus/features/saved-views.md +++ b/docs/docs-beta/docs/dagster-plus/features/catalog-views.md @@ -1,11 +1,8 @@ --- -title: "Saving asset filters as catalog views" -displayed_sidebar: "dagsterPlus" +title: "Catalog views" sidebar_position: 100 --- -# Saving asset filters as catalog views - Catalog views enable you to filter down your view of the Dagster Asset catalog in Dagster+, allowing you to toggle between sets of assets that you care about most. You can save catalog views for your own use or share them with your team. For example, you could create views that: @@ -27,7 +24,7 @@ In this guide, you'll learn how to create, access, and share catalog views with -## Create catalog views +## Creating catalog views To view the Dagster+ Asset catalog, use the **Catalog** button on the top navigation. @@ -39,7 +36,7 @@ To create a new catalog view, you have two options: 1. Create a new catalog view from scratch, from the catalog view menu. 2. Create a new catalog view from your current set of filters. -### Create a new catalog view from scratch +### Creating a new catalog view from scratch 1. Click the catalog view button to open the catalog view menu. From here, click the **New** button. 2. Give the view a name and optionally, a description and icon. @@ -51,7 +48,7 @@ To create a new catalog view, you have two options: Give your view a name and optionally a description and icon. Next, you can select one or more filters to apply to your view by clicking the "Add filters" button. Filters can select a subset of assets based on their metadata, tags, kinds, owners, asset groups, or other properties. -### Create a new catalog view from your current set of filters +### Creating a new catalog view from your current set of filters When viewing the global asset lineage or asset list, you can create a new catalog view from your current set of filters. @@ -61,7 +58,7 @@ When viewing the global asset lineage or asset list, you can create a new catalo 4. To make the view shareable, toggle the **Public view** switch. 5. Click **Create view** to create the view. -## Edit, duplicate, or delete catalog views +## Editing, duplicating, or deleting catalog views 1. Click the catalog view button to open the catalog view menu. 2. Search for the view you want to edit, duplicate, or delete. diff --git a/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/change-tracking.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/change-tracking.md new file mode 100644 index 0000000000000..f798ce75e47bd --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/change-tracking.md @@ -0,0 +1,7 @@ +--- +title: "Change tracking in branch deployments" +sidebar_position: 200 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/managing-deployments/branch-deployments/change-tracking */} diff --git a/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/dagster-cloud-cli.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/dagster-cloud-cli.md new file mode 100644 index 0000000000000..f5af56c5b9abe --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/dagster-cloud-cli.md @@ -0,0 +1,7 @@ +--- +title: Using branch deployments with the dagster-cloud CLI +sidebar_position: 300 +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/managing-deployments/dagster-plus-cli#using-the-dagster-cloud-cli */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/index.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/index.md new file mode 100644 index 0000000000000..39e2db6935879 --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/index.md @@ -0,0 +1,8 @@ +--- +title: Branch deployments +sidebar_position: 20 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/setting-up-branch-deployments.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/setting-up-branch-deployments.md similarity index 95% rename from docs/docs-beta/docs/dagster-plus/features/branch-deployments/setting-up-branch-deployments.md rename to docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/setting-up-branch-deployments.md index 39ef33b1362cb..79c27ab7f9383 100644 --- a/docs/docs-beta/docs/dagster-plus/features/branch-deployments/setting-up-branch-deployments.md +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/setting-up-branch-deployments.md @@ -1,8 +1,6 @@ --- title: "Setting up branch deployments" -displayed_sidebar: "dagsterPlus" sidebar_position: 100 -sidebar_label: "Setting up branch deployments" --- In this guide, we'll walk you through setting up Branch Deployments for a code location. Once you're finished, any time a PR is created or updated in your repository, it will automatically create or update an associated branch deployment in Dagster+. @@ -76,7 +74,7 @@ Keep the token somewhere handy - you'll need it to complete the setup. ## Step 3: Create and configure an agent :::note -If using [Serverless deployment](/dagster-plus/deployment/serverless), this step can be skipped. +If using [Serverless deployment](/dagster-plus/deployment/deployment-types/serverless), this step can be skipped. ::: While you can use your existing production agent, we recommend creating a dedicated branch deployment agent. This ensures that your production instance isn't negatively impacted by the workload associated with branch deployments. @@ -84,7 +82,7 @@ While you can use your existing production agent, we recommend creating a dedica - 1. **Deploy an ECS agent to serve your branch deployments**. Follow the [ECS agent](/dagster-plus/deployment/hybrid/agents/amazon-ecs-new-vpc) setup guide, making sure to set the **Enable Branch Deployments** parameter if using the CloudFormation template. If you are running an existing agent, follow the [upgrade guide](/dagster-plus/deployment/hybrid/agents/amazon-ecs-existing-vpc) to ensure your template is up-to-date. Then, turn on the **Enable Branch Deployments** parameter. + 1. **Deploy an ECS agent to serve your branch deployments**. Follow the [ECS agent](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/new-vpc) setup guide, making sure to set the **Enable Branch Deployments** parameter if using the CloudFormation template. If you are running an existing agent, follow the [upgrade guide](/dagster-plus/deployment/deployment-types/hybrid/amazon-ecs/existing-vpc) to ensure your template is up-to-date. Then, turn on the **Enable Branch Deployments** parameter. 2. **Create a private [Amazon Elastic Registry (ECR) repository](https://console.aws.amazon.com/ecr/repositories).** Refer to the [AWS ECR documentation](https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-create.html) for instructions. @@ -108,7 +106,7 @@ While you can use your existing production agent, we recommend creating a dedica - 1. Set up a new Docker agent. Refer to the [Docker agent setup guide](/dagster-plus/deployment/hybrid/agents/docker) for instructions. + 1. Set up a new Docker agent. Refer to the [Docker agent setup guide](/dagster-plus/deployment/deployment-types/hybrid/docker) for instructions. 2. After the agent is set up, modify the `dagster.yaml` file as follows: - Set the `dagster_cloud_api.branch_deployments` field to `true` @@ -121,7 +119,7 @@ While you can use your existing production agent, we recommend creating a dedica - 1. Set up a new Kubernetes agent. Refer to the [Kubernetes agent setup guide](/dagster-plus/deployment/hybrid/agents/kubernetes) for instructions. + 1. Set up a new Kubernetes agent. Refer to the [Kubernetes agent setup guide](/dagster-plus/deployment/deployment-types/hybrid/kubernetes) for instructions. 2. After the agent is set up, modify your Helm values file to include the following: @@ -444,5 +442,5 @@ dagster-cloud deployment add-location \ ## Next steps -- Learn more about [Branch Deployments](/dagster-plus/features/branch-deployments/index.mdx) -- Learn how to [Track changes on a Branch Deployment](/dagster-plus/features/branch-deployments/change-tracking) +- Learn more about [Branch Deployments](/dagster-plus/features/ci-cd/branch-deployments/index.md) +- Learn how to [Track changes on a Branch Deployment](/dagster-plus/features/ci-cd/branch-deployments/change-tracking) diff --git a/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/testing.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/testing.md new file mode 100644 index 0000000000000..8106ced129daa --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/branch-deployments/testing.md @@ -0,0 +1,7 @@ +--- +title: Testing against production with branch deployments +sidebar_position: 400 +unlisted: true +--- + +{/* TODO move from https://docs.dagster.io/guides/dagster/branch_deployments#testing-against-production-with-dagster-branch-deployments */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/ci-cd/ci-cd-file-reference.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/ci-cd-file-reference.md new file mode 100644 index 0000000000000..21c585c75361c --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/ci-cd-file-reference.md @@ -0,0 +1,6 @@ +--- +title: CI/CD file reference +unlisted: true +--- + +{/* TODO copy from https://docs.dagster.io/dagster-plus/references/ci-cd-file-reference */} \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/ci-cd/index.md b/docs/docs-beta/docs/dagster-plus/features/ci-cd/index.md new file mode 100644 index 0000000000000..27f8c4ab52dba --- /dev/null +++ b/docs/docs-beta/docs/dagster-plus/features/ci-cd/index.md @@ -0,0 +1,8 @@ +--- +title: "CI/CD" +sidebar_position: 30 +--- + +import DocCardList from '@theme/DocCardList'; + + \ No newline at end of file diff --git a/docs/docs-beta/docs/dagster-plus/features/data-catalog.md b/docs/docs-beta/docs/dagster-plus/features/data-catalog.md index 41afe2b6a7bed..bed4e9bfef93e 100644 --- a/docs/docs-beta/docs/dagster-plus/features/data-catalog.md +++ b/docs/docs-beta/docs/dagster-plus/features/data-catalog.md @@ -1,7 +1,6 @@ --- title: "Data catalog" -unlisted: true sidebar_position: 200 +unlisted: true --- -# Dagster+ data catalog diff --git a/docs/docs-beta/docs/dagster-plus/features/insights/export-metrics.md b/docs/docs-beta/docs/dagster-plus/features/insights/export-metrics.md index 3651b20fdbf4e..219eee2060f41 100644 --- a/docs/docs-beta/docs/dagster-plus/features/insights/export-metrics.md +++ b/docs/docs-beta/docs/dagster-plus/features/insights/export-metrics.md @@ -5,4 +5,3 @@ sidebar_position: 200 unlisted: true --- -# Export metrics from Dagster+ Insights diff --git a/docs/docs-beta/docs/dagster-plus/features/insights/index.md b/docs/docs-beta/docs/dagster-plus/features/insights/index.md index a36a2e9513a76..994cc938df500 100644 --- a/docs/docs-beta/docs/dagster-plus/features/insights/index.md +++ b/docs/docs-beta/docs/dagster-plus/features/insights/index.md @@ -1,11 +1,10 @@ --- -title: 'Insights' +title: Dagster+ Insights +sidebar_label: 'Insights' description: 'Visiblity into historical usage, cost, and metadata.' -sidebar_position: 10 +sidebar_position: 50 --- -# Dagster+ Insights - Using Dagster+ Insights, you can gain visibility into historical usage and cost metrics such as Dagster+ run duration, credit usage, and failures. You can also define your own custom metrics, such as the number of rows processed by an asset. Visualizations are built into the Dagster+ UI, allowing you to explore metrics from Dagster and external systems, such as Google BigQuery, in one place. diff --git a/docs/docs-beta/docs/dagster-plus/getting-started.md b/docs/docs-beta/docs/dagster-plus/getting-started.md index 52b79f7b13418..fb4214b62e4ce 100644 --- a/docs/docs-beta/docs/dagster-plus/getting-started.md +++ b/docs/docs-beta/docs/dagster-plus/getting-started.md @@ -1,10 +1,7 @@ --- title: "Getting started with Dagster+" -displayed_sidebar: "dagsterPlus" --- -# Getting started with Dagster+ - First [create a Dagster+ organization](https://dagster.plus/signup). Note: you can sign up with: - a Google email address - a GitHub account @@ -12,9 +9,9 @@ First [create a Dagster+ organization](https://dagster.plus/signup). Note: you c Next, pick your deployment type. Not sure? -- [Dagster+ Serverless](/dagster-plus/deployment/serverless) is the easiest way to get started and is great for teams with limited DevOps support. In Dagster+ Serverless, your Dagster code is executed in Dagster+. You will need to be okay [giving Dagster+ the credentials](/dagster-plus/deployment/environment-variables) to connect to the tools you want to orchestrate. +- [Dagster+ Serverless](/dagster-plus/deployment/deployment-types/serverless) is the easiest way to get started and is great for teams with limited DevOps support. In Dagster+ Serverless, your Dagster code is executed in Dagster+. You will need to be okay [giving Dagster+ the credentials](/dagster-plus/deployment/management/environment-variables) to connect to the tools you want to orchestrate. -- [Dagster+ Hybrid](/dagster-plus/deployment/hybrid) is great for teams who want to orchestrate tools without giving Dagster+ direct access to your systems. Dagster+ Hybrid requires more DevOps support. +- [Dagster+ Hybrid](/dagster-plus/deployment/deployment-types/hybrid) is great for teams who want to orchestrate tools without giving Dagster+ direct access to your systems. Dagster+ Hybrid requires more DevOps support. The remaining steps depend on your deployment type. @@ -40,7 +37,7 @@ See the guide on [adding code locations](/dagster-plus/deployment/code-locations ## Install a Dagster+ Hybrid agent -Follow [these guides](/dagster-plus/deployment/hybrid) for installing a Dagster+ Hybrid agent. Not sure which agent to pick? We recommend using the Dagster+ Kubernetes agent in most cases. +Follow [these guides](/dagster-plus/deployment/deployment-types/hybrid) for installing a Dagster+ Hybrid agent. Not sure which agent to pick? We recommend using the Dagster+ Kubernetes agent in most cases. ## Setup CI/CD @@ -58,4 +55,4 @@ Refer to the guide for [adding a code location](/dagster-plus/deployment/code-lo ## Next steps -Your Dagster+ account is automatically enrolled in a trial. You can [pick your plan type and enter your billing information](/dagster-plus/deployment/dagster-plus-settings), or [contact the Dagster team](https://dagster.io/contact) if you need support or want to evaluate the Dagster+ Pro plan. +Your Dagster+ account is automatically enrolled in a trial. You can [pick your plan type and enter your billing information](/dagster-plus/deployment/management/settings/dagster-plus-settings), or [contact the Dagster team](https://dagster.io/contact) if you need support or want to evaluate the Dagster+ Pro plan. diff --git a/docs/docs-beta/docs/dagster-plus/index.md b/docs/docs-beta/docs/dagster-plus/index.md index 295a68941b406..fa8e16a0df269 100644 --- a/docs/docs-beta/docs/dagster-plus/index.md +++ b/docs/docs-beta/docs/dagster-plus/index.md @@ -1,16 +1,13 @@ --- title: "About Dagster+" -displayed_sidebar: 'dagsterPlus' sidebar_position: 1 --- -# About Dagster+ - Dagster+ is a managed orchestration platform built on top of Dagster's open source engine. Dagster+ is built to be the most performant, reliable, and cost effective way for data engineering teams to run Dagster in production. Dagster+ is also great for students, researchers, or individuals who want to explore Dagster with minimal overhead. -Dagster+ comes in two flavors: a fully [Serverless](/dagster-plus/deployment/serverless) offering and a [Hybrid](/dagster-plus/deployment/hybrid) offering. In both cases, Dagster+ does the hard work of managing your data orchestration control plane. Compared to a [Dagster open source deployment](/guides/), Dagster+ manages: +Dagster+ comes in two flavors: a fully [Serverless](/dagster-plus/deployment/deployment-types/serverless) offering and a [Hybrid](/dagster-plus/deployment/deployment-types/hybrid) offering. In both cases, Dagster+ does the hard work of managing your data orchestration control plane. Compared to a [Dagster open source deployment](/guides/), Dagster+ manages: - Dagster's web UI at https://dagster.plus - Metadata stores for data cataloging and cost insights @@ -24,7 +21,7 @@ In addition to managed infrastructure, Dagster+ also adds core capabilities on t - [Alerts](/dagster-plus/features/alerts) to a variety of services like Slack, PagerDuty, and email to notify your team of failed runs, data quality issues, and violated SLAs. - Authentication, [Role Based Access Control](/dagster-plus/features/authentication-and-access-control/rbac), and [Audit Logs](/dagster-plus/features/authentication-and-access-control/rbac/audit-logs) which help teams implement data mesh strategies while remaining compliant. - [Data Catalog](/dagster-plus/features/data-catalog), a powerful search-first experience that builds off of Dagster's best-in-class lineage graph to include searching for assets, metadata, column lineage, and more. -- [Branch Deployments](/dagster-plus/features/branch-deployments/index.mdx) +- [Branch Deployments](/dagster-plus/features/ci-cd/branch-deployments/index.md) Ready to [get started](/dagster-plus/getting-started)? diff --git a/docs/docs-beta/docs/guides/build/configure/managing-concurrency.md b/docs/docs-beta/docs/guides/build/configure/managing-concurrency.md index 59efe3ac2fe5d..133c36e7cf9a6 100644 --- a/docs/docs-beta/docs/guides/build/configure/managing-concurrency.md +++ b/docs/docs-beta/docs/guides/build/configure/managing-concurrency.md @@ -21,7 +21,7 @@ You often want to control the number of concurrent runs for a Dagster job, a spe * Dagster Core, add the following to your [dagster.yaml](/todo) -* In Dagster+, add the following to your [deployment settings](/dagster-plus/deployment/deployment-settings) +* In Dagster+, add the following to your [deployment settings](/dagster-plus/deployment/management/settings/deployment-settings) ```yaml run_queue: @@ -144,7 +144,7 @@ The possible causes for runs remaining in `QUEUED` status depend on whether you' If runs aren't being dequeued in Dagster+, the root causes could be: - * **If using a [hybrid deployment](/dagster-plus/deployment/hybrid)**, the agent serving the deployment may be down. In this situation, runs will be paused. + * **If using a [hybrid deployment](/dagster-plus/deployment/deployment-types/hybrid)**, the agent serving the deployment may be down. In this situation, runs will be paused. * **Dagster+ is experiencing downtime**. Check the [status page](https://dagstercloud.statuspage.io/) for the latest on potential outages.