Merge branch 'current' into patch-1

.github/ISSUE_TEMPLATE/add-adapter-to-trusted-list.yml → .github/ISSUE_TEMPLATE/zzz_add-adapter-to-trusted-list.yml

@@ -41,11 +41,5 @@ body:
         - label: I am a maintainer of the adapter being submited for Trusted status
         - label: I have read both the [Trusted adapters](https://docs.getdbt.com/docs/trusted-adapters) and [Building a Trusted Adapter](https://docs.getdbt.com/guides/dbt-ecosystem/adapter-development/8-building-a-trusted-adapter) pages.
         - label: I believe that the adapter currently meets the expectations given above
-- label: I will ensure this adapter stays in compliance with the guidelines 
+        - label: I will ensure this adapter stays in compliance with the guidelines 
         - label: I understand that dbt Labs reserves the right to remove an adapter from the trusted adapter list at any time, should any of the below guidelines not be met
-    validations:
-      required: true
-
-
-
-

website/docs/docs/cloud/about-cloud/regions-ip-addresses.md

@@ -11,10 +11,17 @@ dbt Cloud is [hosted](/docs/cloud/about-cloud/architecture) in multiple regions
 
 | Region | Location | Access URL | IP addresses | Developer plan | Team plan | Enterprise plan |
 |--------|----------|------------|--------------|----------------|-----------|-----------------|
-| North America [^1] | AWS us-east-1 (N. Virginia) | cloud.getdbt.com | 52.45.144.63 <br /> 54.81.134.249 <br />52.22.161.231 | ✅ | ✅ | ✅ |
+| North America multi-tenant [^1] | AWS us-east-1 (N. Virginia) | cloud.getdbt.com | 52.45.144.63 <br /> 54.81.134.249 <br />52.22.161.231 | ✅ | ✅ | ✅ |
+| North America Cell 1 [^1]       | AWS use-east-1 (N.Virginia) | {account prefix}.us1.dbt.com | [Located in Account Settings](#locating-your-dbt-cloud-ip-addresses) | ❌ | ❌ | ❌ |
 | EMEA [^1] | AWS eu-central-1	(Frankfurt) | emea.dbt.com | 3.123.45.39 <br /> 3.126.140.248 <br /> 3.72.153.148 | ❌ | ❌ | ✅ |
 | APAC  [^1] | 	AWS ap-southeast-2  (Sydney)| au.dbt.com | 52.65.89.235 <br /> 3.106.40.33 <br /> 13.239.155.206 <br />| ❌ | ❌ | ✅ |
 | Virtual Private dbt or Single tenant | Customized |  Customized | Ask [Support](/community/resources/getting-help#dbt-cloud-support) for your IPs | ❌ | ❌ | ✅ |
 
 
 [^1]: These regions support [multi-tenant](/docs/cloud/about-cloud/tenancy) deployment environments hosted by dbt Labs.
+
+### Locating your dbt Cloud IP addresses
+
+There are two ways to view your dbt Cloud IP addresses:
+- If no projects exist in the account, create a new project, and the IP addresses will be displayed during the **Configure your environment** steps.
+- If you have an existing project, navigate to **Account Settings** and ensure you are in the **Projects** pane. Click on a project name, and the **Project Settings** window will open. Locate the **Connection** field and click on the name. Scroll down to the **Settings**, and the first text block lists your IP addresses. 

website/docs/docs/cloud/billing.md

@@ -15,7 +15,7 @@ As a customer, you pay for the number of seats you have and the amount of usage
 
 dbt Cloud considers a Successful Model Built as any model that is successfully built via a run through dbt Cloud’s orchestration functionality in a dbt Cloud deployment environment. Models are counted when built and run. This includes any jobs run via dbt Cloud's scheduler, CI builds (jobs triggered by pull requests), runs kicked off via the dbt Cloud API, and any successor dbt Cloud tools with similar functionality. This also includes models that are successfully built even when a run may fail to complete. For example, you may have a job that contains 100 models and on one of its runs, 51 models are successfully built and then the job fails. In this situation, only 51 models would be counted.
 
-Any models built in a dbt Cloud development environment (for example, via the IDE) do not count towards your usage. Tests, seeds, and snapshots also do not count. 
+Any models built in a dbt Cloud development environment (for example, via the IDE) do not count towards your usage. Tests, seeds, ephemeral models, and snapshots also do not count. 
 
 
 ### What counts as a seat license? 

website/docs/docs/cloud/manage-access/set-up-sso-google-workspace.md

@@ -49,7 +49,7 @@ Client Secret for use in dbt Cloud.
 | **Application type**   | internal     | required |
 | **Application name**   | dbt Cloud    | required |
 | **Application logo**   | Download the logo <a href="https://www.getdbt.com/ui/img/dbt-icon.png" target="_blank" rel="noopener noreferrer">here</a> | optional |
-| **Authorized domains** | `getdbt.com` (US) `dbt.com` (EMEA or AU) | If deploying into a VPC, use the domain for your deployment |
+| **Authorized domains** | `getdbt.com` (US multi-tenant) `getdbt.com` and `dbt.com`(US Cell 1) `dbt.com` (EMEA or AU) | If deploying into a VPC, use the domain for your deployment |
 | **Scopes** | `email, profile, openid` | The default scopes are sufficient |
 
 <Lightbox src="/img/docs/dbt-cloud/dbt-cloud-enterprise/gsuite/gsuite-sso-consent-top.png" title="GSuite Consent Screen configuration"/>

website/docs/docs/deploy/webhooks.md

@@ -167,20 +167,21 @@ An example of a webhook payload for an errored run:
 You can use the dbt Cloud API to create new webhooks that you want to subscribe to, get detailed information about your webhooks, and to manage the webhooks that are associated with your account. The following sections describe the API endpoints you can use for this. 
 
 :::info Access URLs
-dbt Cloud is hosted in multiple regions in the world and each region has a different access URL. People on Enterprise plans can choose to have their account hosted in any one of these regions. This section uses `cloud.getdbt.com` (which is for North America) as part of the endpoint but your access URL might be different. For a complete list of available dbt Cloud access URLs, refer to [Regions & IP addresses](/docs/cloud/about-cloud/regions-ip-addresses).   
+dbt Cloud is hosted in multiple regions in the world and each region has a different access URL. People on Enterprise plans can choose to have their account hosted in any one of these regions. For a complete list of available dbt Cloud access URLs, refer to [Regions & IP addresses](/docs/cloud/about-cloud/regions-ip-addresses).   
 :::
 
 ### List all webhook subscriptions
 List all webhooks that are available from a specific dbt Cloud account.
 
 #### Request 
 ```shell
-GET https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscriptions
+GET https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscriptions
 ```
 
 #### Path parameters
 | Name       | Description                          |
 |------------|--------------------------------------|
+| `your access URL` | The login URL for your dbt Cloud account. |
 | `account_id` | The dbt Cloud account the webhooks are associated with. |
 
 #### Response sample
@@ -265,11 +266,12 @@ Get detailed information about a specific webhook.
 
 #### Request
 ```shell
-GET https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}
+GET https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}
 ```
 #### Path parameters
 | Name       | Description                          |
 |------------|--------------------------------------|
+| `your access URL` | The login URL for your dbt Cloud account. |
 | `account_id` | The dbt Cloud account the webhook is associated with. |
 | `webhook_id` | The webhook you want detailed information on. |
 
@@ -322,7 +324,7 @@ Create a new outbound webhook and specify the endpoint URL that will be subscrib
 #### Request sample
 
 ```shell
-POST https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscriptions
+POST https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscriptions
 ```
 
 ```json
@@ -344,6 +346,7 @@ POST https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscription
 #### Path parameters
 | Name | Description |
 | --- | --- |
+| `your access URL` | The login URL for your dbt Cloud account. |
 | `account_id` | The dbt Cloud account the webhook is associated with. |
 
 #### Request parameters
@@ -407,7 +410,7 @@ Update the configuration details for a specific webhook.
 
 #### Request sample
 ```shell
-PUT https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}
+PUT https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}
 ```
 
 ```json
@@ -429,6 +432,7 @@ PUT https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscription/
 #### Path parameters
 | Name       | Description                          |
 |------------|--------------------------------------|
+| `your access URL` | The login URL for your dbt Cloud account. |
 | `account_id` | The dbt Cloud account the webhook is associated with. |
 | `webhook_id` | The webhook you want to update. |
 
@@ -491,12 +495,13 @@ Test a specific webhook.
 
 #### Request
 ```shell
-GET https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}/test
+GET https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}/test
 ```
 
 #### Path parameters
 | Name       | Description                          |
 |------------|--------------------------------------|
+| `your access URL` | The login URL for your dbt Cloud account. |
 | `account_id` | The dbt Cloud account the webhook is associated with. |
 | `webhook_id` | The webhook you want to test.  |
 
@@ -518,12 +523,13 @@ Delete a specific webhook.
 
 #### Request
 ```shell
-DELETE https://cloud.getdbt.com/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}
+DELETE https://{your access URL}/api/v3/accounts/{account_id}/webhooks/subscription/{webhook_id}
 ```
 
 #### Path parameters
 | Name       | Description                          |
 |------------|--------------------------------------|
+| `your access URL` | The login URL for your dbt Cloud account. |
 | `account_id` | The dbt Cloud account the webhook is associated with. |
 | `webhook_id` | The webhook you want to delete. |
 

website/docs/faqs/Accounts/cloud-upgrade-instructions.md

@@ -38,7 +38,7 @@ To unlock your account and select a plan, review the following guidance per plan
 2. To unlock your account and continue using the Team plan, you need to enter your payment details. 
 3. Go to **Payment Information** and click **Edit** on the right.
 4. Enter your payment details and click **Save**.
-5.  This automatically unlocks your dbt Cloud account, and you can now enjoy the benefits of the Team plan. 🎉
+5. This automatically unlocks your dbt Cloud account, and you can now enjoy the benefits of the Team plan. 🎉
 
 <Lightbox src="/img/docs/dbt-cloud/trial-team-flow.gif"/>
 
@@ -59,7 +59,7 @@ For commonly asked billings questions, refer to the dbt Cloud [pricing page](htt
 <details>
   <summary>How does billing work?</summary>
   <div>
-    <div>Team plans are billed monthly on the credit card used to sign up, based on <a href="https://www.getdbt.com/pricing/">developer seat count</a>. You’ll also be sent a monthly receipt to the billing email of your choice. You can change any billing information in your <b>Account Settings</b> -> <b>Billing page</b>. <br></br><br></br>
+    <div>Team plans are billed monthly on the credit card used to sign up, based on [developer seat count and usage](/docs/cloud/billing). You’ll also be sent a monthly receipt to the billing email of your choice. You can change any billing information in your <b>Account Settings</b> > <b>Billing page</b>. <br></br><br></br>
 
     Enterprise plan customers are billed annually based on the number of developer seats, as well as any additional services + features in your chosen plan. </div>
     </div>
@@ -75,7 +75,7 @@ For commonly asked billings questions, refer to the dbt Cloud [pricing page](htt
 <details>
   <summary>Can I pay by invoice?</summary>
     <div>
-      <div>At present, dbt Cloud Team plan payments must be made via credit card, and by default they will be billed monthly based on the number of developer seats. <br></br><br></br>
+      <div>Currently, dbt Cloud Team plan payments must be made with a credit card, and by default they will be billed monthly based on the number of [developer seats and usage](/docs/cloud/billing). <br></br><br></br>
       
       We don’t have any plans to do invoicing for Team plan accounts in the near future, but we do currently support invoices for companies on the dbt Cloud Enterprise plan. Feel free to <a href="https://www.getdbt.com/contact/">contact</a> us to build your Enterprise pricing plan.</div> 
     </div> 

website/docs/faqs/Accounts/payment-accepted.md

@@ -5,6 +5,6 @@ sidebar_label: 'Can I pay invoice'
 id: payment-accepted
 ---
 
-Presently for Team plans, self-service dbt Cloud payments must be made via credit card and by default, they will be billed monthly based on the number of active developer seats.
+Currently for Team plans, self-service dbt Cloud payments must be made with a credit card and by default, they will be billed monthly based on the number of [active developer seats and usage](/docs/cloud/billing).
 
 We don't have any plans to do invoicing for self-service teams in the near future, but we *do* currently support invoices for companies on the **dbt Cloud Enterprise plan.** Feel free to [contact us](https://www.getdbt.com/contact) to build your Enterprise pricing.

website/docusaurus.config.js

@@ -51,6 +51,7 @@ var siteSettings = {
     docs:{
       sidebar: {
         hideable: true,
+        autoCollapseCategories: true,
       },
     },
     image: "/img/avatar.png",

website/snippets/auth0-uri.md

@@ -3,7 +3,8 @@ The URI used for SSO connections on multi-tenant dbt Cloud instances will vary b
 
 | Region | dbt Cloud Access URL | Auth0 SSO URI <YOUR_AUTH0_URI> | Auth0 Entity ID <YOUR_AUTH0_ENTITYID>* |
 |--------|-----------------------|-------------------------------|----------------------------------------|
-| US     | cloud.getdbt.com     | auth.cloud.getdbt.com | us-production-mt                       |
+| US multi-tenant   | cloud.getdbt.com      | auth.cloud.getdbt.com | us-production-mt                       |
+| US cell 1 | {account prefix}.us1.dbt.com | auth.cloud.getdbt.com | us-production-mt |
 | EMEA   | emea.dbt.com         | auth.emea.dbt.com     | emea-production-mt                     |
 | APAC   | au.dbt.com           | auth.au.dbt.com       | au-production-mt                       |