Merge branch 'current' into dbt-teradata-1.8.x

website/docs/docs/cloud/migration.md

@@ -1,6 +1,7 @@
 --- 
 title: "Multi-cell migration checklist"
 id: migration 
+sidebar_label: "Multi-cell migration checklist"
 description: "Prepare for account migration to AWS cell-based architecture." 
 pagination_next: null
 pagination_prev: null
@@ -16,17 +17,15 @@ This document outlines the steps that you must take to prevent service disruptio
 
 ## Pre-migration checklist
 
-Prior to your migration date, your dbt Cloud account admin will need to make some changes to your account.
+Prior to your migration date, your dbt Cloud account admin will need to make some changes to your account. Most of your configurations will be migrated automatically, but a few will require manual intervention. 
 
 If your account is scheduled for migration, you will see a banner indicating your migration date when you log in. If you don't see a banner, you don't need to take any action.
 
 1. **IP addresses** — dbt Cloud will be using new IPs to access your warehouse after the migration. Make sure to allow inbound traffic from these IPs in your firewall and include it in any database grants. All six of the IPs below should be added to allowlists.
     * Old IPs: `52.45.144.63`, `54.81.134.249`, `52.22.161.231`
     * New IPs: `52.3.77.232`, `3.214.191.130`, `34.233.79.135`
-2. **IDE sessions** — Any uncommitted changes in the IDE might be lost during the migration process. dbt Labs _strongly_ encourages you to commit all changes in the IDE before your scheduled migration time.
-3. **User invitations** — Any pending user invitations will be invalidated during the migration. You can resend the invitations once the migration is complete.
-4. **Git integrations** — For customers on a dbt Cloud Enterprise plan, native integrations with [GitLab](/docs/cloud/git/connect-gitlab#for-the-dbt-cloud-enterprise-tier) and [Azure DevOps](/docs/cloud/git/connect-azure-devops) will need to be manually updated. dbt Labs will not be migrating any accounts using these integrations at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration.
-5. **SSO integrations** — Integrations with SSO identity providers (IdPs) will need to be manually updated. dbt Labs will not be migrating any accounts using SSO at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration.
+2. **User invitations** — Any pending user invitations will be invalidated during the migration. You can resend the invitations after the migration is complete.
+3. **SSO integrations** — If you've completed the Auth0 migration, your account SSO configurations will be automatically transferred. If you haven't completed the Auth0 migration, dbt Labs recommends doing that before starting the mult-cell migration to avoid service disruptions.
 
 ## Post-migration
 

website/docs/docs/dbt-cloud-apis/apis-overview.md

@@ -6,7 +6,7 @@ pagination_next: "docs/dbt-cloud-apis/user-tokens"
 pagination_prev: null
 ---
 
-## Overview
+# APIs overview <Lifecycle status="team,enterprise"/>
 
 Accounts on the _Team_ and _Enterprise_ plans can query the dbt Cloud APIs.
 

website/docs/docs/dbt-cloud-apis/service-tokens.md

@@ -3,6 +3,9 @@ title: "Service account tokens"
 id: "service-tokens"
 description: "Service account tokens help you define permissions for securing access to your dbt Cloud account and its projects."
 ---
+
+# Service account tokens <Lifecycle status="team,enterprise"/>
+
 :::info Important service account token update
 
 If you have service tokens created on or before July 18, 2023, please read [this important update](/docs/dbt-cloud-apis/service-tokens#service-token-update).

website/docs/docs/dbt-cloud-apis/user-tokens.md

@@ -4,6 +4,8 @@ id: "user-tokens"
 pagination_next: "docs/dbt-cloud-apis/service-tokens"
 ---
 
+# User tokens <Lifecycle status="team,enterprise"/>
+
 :::note Announcement
 
 The [user API tokens](#user-tokens) are being replaced by [account-scoped personal access tokens(PATs)](#account-scoped-personal-access-tokens). We recommend rotating your existing user tokens with PATs. There are no deprecation plans for user API tokens at this time; we will give ample notice when that timeline has been determined. 

website/docs/reference/database-permissions/postgres-permissions.md

@@ -9,17 +9,25 @@ In Postgres, permissions are used to control who can perform certain actions on
 
 The following example provides you with the SQL statements you can use to manage permissions. These examples allow you to run dbt smoothly without encountering permission issues, such as creating schemas, reading existing data, and accessing the information schema. 
 
-**Note** that `database_name`, `database.schema_name`, and `user_name` are placeholders and you can replace them as needed for your organization's naming convention.
+**Note** that `database_name`, `source_schema`, `destination_schema`, and `user_name` are placeholders and you can replace them as needed for your organization's naming convention.
 
-```
-grant usage on database database_name to user_name;
-grant create schema on database database_name to user_name;
-grant usage on schema database.schema_name to user_name;
-grant create table on schema database.schema_name to user_name;
-grant create view on schema database.schema_name to user_name;
-grant usage on all schemas in database database_name to user_name;
-grant select on all tables in database database_name to user_name;
-grant select on all views in database database_name to user_name;
+```sql
+grant connect on database database_name to user_name;
+
+-- Grant read permissions on the source schema
+grant usage on schema source_schema to user_name;
+grant select on all tables in schema source_schema to user_name;
+alter default privileges in schema source_schema grant select on tables to user_name;
+
+-- Create destination schema and make user_name the owner
+create schema if not exists destination_schema;
+alter schema destination_schema owner to user_name;
+
+-- Grant write permissions on the destination schema
+grant usage on schema destination_schema to user_name;
+grant create on schema destination_schema to user_name;
+grant insert, update, delete, truncate on all tables in schema destination_schema to user_name;
+alter default privileges in schema destination_schema grant insert, update, delete, truncate on tables to user_name;
 ```
 
 Check out the [official documentation](https://www.postgresql.org/docs/current/sql-grant.html) for more information.

website/docusaurus.config.js

@@ -133,6 +133,11 @@ var siteSettings = {
             },
           ],
         },
+        {
+          to: "/guides",
+          label: "Guides",
+          position: "left",
+        },
         {
           to: "reference/references-overview",
           label: "Reference",
@@ -151,10 +156,6 @@ var siteSettings = {
               label: "Best Practices",
               to: "/best-practices",
             },
-            {
-              label: "Guides",
-              to: "/guides",
-            },
             {
               label: "Developer Blog",
               to: "/blog",

website/sidebars.js

@@ -51,6 +51,7 @@ const sidebarSettings = {
           items: [
             "docs/cloud/about-cloud-setup",
             "docs/dbt-cloud-environments",
+            "docs/cloud/migration",
             {
               type: "category",
               label: "Connect data platform",

website/src/components/expandable/styles.module.css

@@ -140,5 +140,4 @@
 
 .expandableContainer {
     margin-bottom: 5px; /* Adjust this value as needed to create space */
-  }
-
+}