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 a3b242c3b3fb7..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 @@ -10,7 +10,7 @@ Dagster+ automatically tracks metadata every time a code location is loaded. Thi Before continuing, you should be familiar with: -- [Code Locations](/dagster-plus/features/code-locations) +- [Code Locations](/dagster-plus/deployment/code-locations) diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md index 5a4c660304db3..0b23dc899ee39 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/index.md @@ -32,7 +32,7 @@ The Dagster+ agent is a long-lived process that polls Dagster+'s API servers for ### Code location servers -Dagster+ runs your Dagster projects through code locations. To get started, follow this guide for [adding a code location](/dagster-plus/features/code-locations). +Dagster+ runs your Dagster projects through code locations. To get started, follow this guide for [adding a code location](/dagster-plus/deployment/code-locations). When you inform Dagster+ about a new code location, we enqueue instructions for your agent to launch a new code server. The agent uses your container image to launch a code server that interacts with your Dagster definitions. The agent will run one long-standing code server for each code location. Once the code server is running, the agent will send Dagster+ metadata about your Dagster definitions that Dagster+ uses to make orchestration decisions. diff --git a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md index f6cd53f5dbb09..619f5ffa72326 100644 --- a/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md +++ b/docs/docs-beta/docs/dagster-plus/deployment/deployment-types/hybrid/kubernetes/setup.md @@ -81,7 +81,7 @@ kubectl --namespace dagster-cloud logs -l deployment=agent There are three places to customize how Dagster interacts with Kubernetes: - **Per Deployment** by configuring the Dagster+ agent using [Helm values](https://artifacthub.io/packages/helm/dagster-cloud/dagster-cloud-agent?modal=values) -- **Per Project** by configuring the `dagster_cloud.yaml` file for your [code location](/dagster-plus/features/code-locations) +- **Per Project** by configuring the `dagster_cloud.yaml` file for your [code location](/dagster-plus/deployment/code-locations) - **Per Asset or Job** by adding tags to the [asset](/todo), [job](/todo), or [customizing the Kubernetes pipes invocation](/todo) 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. 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 05b98b558c1e1..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 @@ -47,7 +47,7 @@ Organization Admins have access to the entire organization, including all [deplo | Level | Plan | Description | | ------------------ | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Deployment | All plans | Defines the level of access for a given deployment. Roles set at this level will be the default role for the user or team for all code locations in the deployment.

Note: Granting access to a deployment grants a minimum of Viewer access to all code locations. Preventing access for specific code locations isn't currently supported. Additionally, having access to a deployment doesn't grant access to Branch Deployments - those permissions must be granted separately. | -| Code location | Pro | Defines the level of access for a given code location in a deployment.

Dagster+ Pro users can [override the default deployment-level role for individual code locations](/dagster-plus/features/code-locations). For example, if the Deployment role is Launcher, you could override this role with a more permissive role, such as Editor or Admin.

For non-Pro users, users will have the same level of access for all code locations in a deployment. | +| Code location | Pro | Defines the level of access for a given code location in a deployment.

Dagster+ Pro users can [override the default deployment-level role for individual code locations](/dagster-plus/deployment/code-locations). For example, if the Deployment role is Launcher, you could override this role with a more permissive role, such as Editor or Admin.

For non-Pro users, users will have the same level of access for all code locations in a deployment. | | Branch deployments | All plans | Defines the level of access for all Branch Deployments in the code locations the user or team has access to. | ### Applying role overrides @@ -138,9 +138,9 @@ Code locations are accessed in the UI by navigating to **Deployment > Code locat | | Viewer | Launcher | Editor | Admin | Organization
admin | | ------------------------------------------------------------------------------- | ------ | -------- | ------ | ----- | ------------------------ | -| View [code locations](/dagster-plus/features/code-locations) | ✅ | ✅ | ✅ | ✅ | ✅ | -| Create and remove [code locations](/dagster-plus/features/code-locations) | ❌ | ❌ | ✅ | ✅ | ✅ | -| Reload [code locations](/dagster-plus/features/code-locations) and workspaces | ❌ | ❌ | ✅ | ✅ | ✅ | +| View [code locations](/dagster-plus/deployment/code-locations) | ✅ | ✅ | ✅ | ✅ | ✅ | +| Create and remove [code locations](/dagster-plus/deployment/code-locations) | ❌ | ❌ | ✅ | ✅ | ✅ | +| Reload [code locations](/dagster-plus/deployment/code-locations) and workspaces | ❌ | ❌ | ✅ | ✅ | ✅ | ### Agent tokens diff --git a/docs/docs-beta/docs/dagster-plus/getting-started.md b/docs/docs-beta/docs/dagster-plus/getting-started.md index 468e1a248869e..b515b01891a63 100644 --- a/docs/docs-beta/docs/dagster-plus/getting-started.md +++ b/docs/docs-beta/docs/dagster-plus/getting-started.md @@ -32,7 +32,7 @@ The Dagster+ onboarding will guide you through: If you don't have any Dagster code yet, you can select an example project or import an existing dbt project. ::: -See the guide on [adding code locations](/dagster-plus/features/code-locations) for details. +See the guide on [adding code locations](/dagster-plus/deployment/code-locations) for details. @@ -49,7 +49,7 @@ In most cases, your CI/CD process will be responsible for: - pushing your Docker image to a container registry you manage - notifying Dagster+ of the new or updated code -Refer to the guide for [adding a code location](/dagster-plus/features/code-locations) for more detail. +Refer to the guide for [adding a code location](/dagster-plus/deployment/code-locations) for more detail. diff --git a/docs/docs-beta/docs/guides/deploy/code-locations/workspace-yaml.md b/docs/docs-beta/docs/guides/deploy/code-locations/workspace-yaml.md index 274e479e3fb6b..7c6f2cae608d8 100644 --- a/docs/docs-beta/docs/guides/deploy/code-locations/workspace-yaml.md +++ b/docs/docs-beta/docs/guides/deploy/code-locations/workspace-yaml.md @@ -4,7 +4,7 @@ sidebar_position: 200 --- :::info - This reference is only applicable to Dagster OSS. For Dagster Cloud see [the Dagster Cloud Code Locations guide](/dagster-plus/features/code-locations) + This reference is only applicable to Dagster OSS. For Dagster Cloud see [the Dagster Cloud Code Locations documentation](/dagster-plus/deployment/code-locations) ::: The `workspace.yaml` file is used to configure code locations in Dagster. It tells Dagster where to find your code and how to load it.