diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 85bf20880f8..95e745fe963 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -13,7 +13,7 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr ## Required setup -- You must select the **[Production environment](/docs/deploy/deploy-environments#set-as-production-environment-beta)** checkbox in the **Environment Settings** page. +- You must select the **[Production environment](/docs/deploy/deploy-environments#set-as-production-environment)** checkbox in the **Environment Settings** page. - This can be set for one deployment environment per dbt Cloud project. - You must have a successful job run first. diff --git a/website/docs/docs/collaborate/explore-projects.md b/website/docs/docs/collaborate/explore-projects.md index b041cd0c915..282ef566356 100644 --- a/website/docs/docs/collaborate/explore-projects.md +++ b/website/docs/docs/collaborate/explore-projects.md @@ -17,7 +17,7 @@ Try dbt Explorer! It's available in [Public Preview](/docs/dbt-versions/product- ## Prerequisites - You have a [multi-tenant](/docs/cloud/about-cloud/tenancy#multi-tenant) or AWS single-tenant dbt Cloud account on the [Team or Enterprise plan](https://www.getdbt.com/pricing/). -- You have set up a [production deployment environment](/docs/deploy/deploy-environments#set-as-production-environment-beta) for each project you want to explore. +- You have set up a [production deployment environment](/docs/deploy/deploy-environments#set-as-production-environment) for each project you want to explore. - There has been at least one successful job run in the production deployment environment. - You are on the dbt Explorer page. To do this, select **Explore** from the top navigation bar in dbt Cloud. diff --git a/website/docs/docs/collaborate/govern/project-dependencies.md b/website/docs/docs/collaborate/govern/project-dependencies.md index 9a1d8b59b68..d873d8883d6 100644 --- a/website/docs/docs/collaborate/govern/project-dependencies.md +++ b/website/docs/docs/collaborate/govern/project-dependencies.md @@ -29,7 +29,7 @@ Starting in dbt v1.6 or higher, `packages.yml` has been renamed to `dependencies In order to add project dependencies and resolve cross-project `ref`, you must: - Use dbt v1.6 or higher for **both** the upstream ("producer") project and the downstream ("consumer") project. -- Have a deployment environment in the upstream ("producer") project [that is set to be your production environment](/docs/deploy/deploy-environments#set-as-production-environment-beta) +- Have a deployment environment in the upstream ("producer") project [that is set to be your production environment](/docs/deploy/deploy-environments#set-as-production-environment) - Have a successful run of the upstream ("producer") project - Have a multi-tenant or single-tenant [dbt Cloud Enterprise](https://www.getdbt.com/pricing) account (Azure ST is not supported but coming soon) diff --git a/website/docs/docs/deploy/deploy-environments.md b/website/docs/docs/deploy/deploy-environments.md index bdcf36b7a30..83231e2d66d 100644 --- a/website/docs/docs/deploy/deploy-environments.md +++ b/website/docs/docs/deploy/deploy-environments.md @@ -28,16 +28,12 @@ To create a new dbt Cloud development environment, navigate to **Deploy** -> **E -### Set as production environment (Beta) +### Set as production environment -import ExpBeta from '/snippets/_explorer-beta-banner.md'; - - +In dbt Cloud, each project can have one designated deployment environment, which serves as its production environment. This production environment is _essential_ for using features like dbt Explorer and cross-project references. It acts as the source of truth for the project's production state in dbt Cloud. -In dbt Cloud, each project can have one designated deployment environment, which serves as its production environment. This production environment is _essential_ for using features like dbt Explorer and cross-project references. It acts as the source of truth for the project's production state in dbt Cloud. - ### Semantic Layer For Semantic Layer-eligible customers, the next section of environment settings is the Semantic Layer configurations. [The Semantic Layer setup guide](/docs/use-dbt-semantic-layer/setup-sl) has the most up-to-date setup instructions! diff --git a/website/snippets/_explorer-beta-banner.md b/website/snippets/_explorer-beta-banner.md deleted file mode 100644 index ab501c7bd0f..00000000000 --- a/website/snippets/_explorer-beta-banner.md +++ /dev/null @@ -1,3 +0,0 @@ -:::info Beta -This feature is related to dbt Explorer and cross-project references [beta](/docs/dbt-versions/product-lifecycles#dbt-cloud) projects and subject to change. If you are interested in getting access to the beta, please [contact us](mailto:support@getdbt.com). -::: diff --git a/website/snippets/_explorer-beta-note.md b/website/snippets/_explorer-beta-note.md index 3bdcd5bcf7a..b15bd310a58 100644 --- a/website/snippets/_explorer-beta-note.md +++ b/website/snippets/_explorer-beta-note.md @@ -1 +1 @@ -**Note:** Make sure to set the environment to "Production" so you can take advantage of features like dbt Explorer and cross-project references. Refer to [Set product environment](/docs/deploy/deploy-environments#set-as-production-environment-beta) for details. +**Note:** Make sure to set the environment to "Production" so you can take advantage of features like dbt Explorer and cross-project references. Refer to [Set product environment](/docs/deploy/deploy-environments#set-as-production-environment) for details.