From b3ad0e078a102efcd37fe5fd20cab073a4be065c Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 28 Aug 2024 17:24:58 +0100 Subject: [PATCH] add note about enterprise plans (#5916) add clarifying info that acct-level connections feature isn't yet available to enterprise plans (and free plans) yet. [internal slack thread](https://dbt-labs.slack.com/archives/C05CJT5MJF2/p1722613501740939) --- .../connect-data-platform/about-connections.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/website/docs/docs/cloud/connect-data-platform/about-connections.md b/website/docs/docs/cloud/connect-data-platform/about-connections.md index 0149dd65a32..599645c53aa 100644 --- a/website/docs/docs/cloud/connect-data-platform/about-connections.md +++ b/website/docs/docs/cloud/connect-data-platform/about-connections.md @@ -27,22 +27,21 @@ These connection instructions provide the basic fields required for configuring ## Connection management -:::info Connections are moving! +:::info Connection management now at account-level -Up until July 2024, connections were nested under projects. One dbt Cloud project could only have one connection, which was re-used across all its environments. Extended attributes were leveraged to switch warehouse instances depending on the environment for a given project. +Starting July 2024, connection management has moved from the project level to the account level for all users in dbt Cloud. Previously, each dbt Cloud project could only have one connection, which was used across all its environments. Extended attributes were used to switch warehouse instances depending on the environment for a given project. - + -We are rolling out an important change that moves connection management to the account level. The following connection management section describes these changes. +The following connection management section describes these changes. -This feature is being rolled out in phases over the coming weeks. ::: Warehouse connections are an account-level resource. As such you can find them under **Accounts Settings** > **Connections**: -Warehouse connections can be re-used across projects. If multiple projects all connect to the same warehouse, you should re-use the same connection in order to streamline your management operations. Connections are assigned to a project via an [environment](/docs/dbt-cloud-environments). +Warehouse connections can be re-used across projects. If multiple projects all connect to the same warehouse, you should re-use the same connection to streamline your management operations. Connections are assigned to a project via an [environment](/docs/dbt-cloud-environments). @@ -50,7 +49,7 @@ As shown in the image, a project with 2 environments can target between 1 and 2 ### Migration from project level connections to account level connections -Rolling out account-level connections will not require any interruption of service in your current usage (IDE, CLI, jobs, etc.). +Rolling out account-level connections will not require any interruption of service in your current usage (IDE, CLI, jobs, and so on.). :::info Why am I prompted to configure a development environment? If your project did not previously have a development environment, you may be redirected to the project setup page. Your project is still intact. Choose a connection for your new development environment, and you can view all your environments again. @@ -60,7 +59,7 @@ However, to fully utilize the value of account-level connections, you may have t -Please consider all of the following actions, as the steps you take will depend on the desired outcome. +Please consider the following actions, as the steps you take will depend on the desired outcome. - The initial clean-up of your connection list - Delete unused connections with 0 environments.