Merge branch 'current' into add-hard-deletes-config

dbt-labs · Nov 29, 2024 · fa9af39 · fa9af39
2 parents 95b14cb + b3b2001
commit fa9af39
Show file tree

Hide file tree

Showing 6 changed files with 33 additions and 35 deletions.
diff --git a/website/docs/docs/build/snapshots.md b/website/docs/docs/build/snapshots.md
@@ -530,7 +530,7 @@ Snapshot results:
 
 For information about configuring snapshots in dbt versions 1.8 and earlier, select **1.8** from the documentation version picker, and it will appear in this section.
 
-To configure snapshots in versions 1.9 and later, refer to [Configuring snapshots](#configuring-snapshots). The latest versions use an updated snapshot configuration syntax that optimizes performance.
+To configure snapshots in versions 1.9 and later, refer to [Configuring snapshots](#configuring-snapshots). The latest versions use a more ergonomic snapshot configuration syntax that also speeds up parsing and compilation.
 
 </VersionBlock>
 

diff --git a/website/docs/docs/cloud/connect-data-platform/connect-starburst-trino.md b/website/docs/docs/cloud/connect-data-platform/connect-starburst-trino.md
@@ -11,7 +11,7 @@ The following are the required fields for setting up a connection with a [Starbu
 | **Host** | The hostname of your cluster. Don't include the HTTP protocol prefix. | `mycluster.mydomain.com` |
 | **Port** | The port to connect to your cluster. By default, it's 443 for TLS enabled clusters. | `443` |
 | **User** | The username (of the account) to log in to your cluster. When connecting to Starburst Galaxy clusters, you must include the role of the user as a suffix to the username.<br/><br/> | Format for Starburst Enterprise or Trino depends on your configured authentication method. <br/>Format for Starburst Galaxy:<br/> <ul><li>`[email protected]/role`</li></ul> |
-| **Password** | The user's password. |   |
+| **Password** | The user's password. |  -  |
 | **Database** | The name of a catalog in your cluster. | `example_catalog` |
 | **Schema** | The name of a schema that exists within the specified catalog.  | `example_schema` |
 

diff --git a/website/docs/docs/cloud/git/connect-gitlab.md b/website/docs/docs/cloud/git/connect-gitlab.md
@@ -61,8 +61,8 @@ In GitLab, when creating your Group Application, input the following:
 | ------ | ----- |
 | **Name** | dbt Cloud |
 | **Redirect URI** | `https://YOUR_ACCESS_URL/complete/gitlab` |
-| **Confidential** | ✔️ |
-| **Scopes** | ✔️ api |
+| **Confidential** | ✅ |
+| **Scopes** | ✅ api |
 
 Replace `YOUR_ACCESS_URL` with the [appropriate Access URL](/docs/cloud/about-cloud/access-regions-ip-addresses) for your region and plan.
 

diff --git a/website/docs/docs/cloud/manage-access/self-service-permissions.md b/website/docs/docs/cloud/manage-access/self-service-permissions.md
@@ -52,33 +52,33 @@ The following tables outline the access that users have if they are assigned a D
 
 | Account-level permission| Owner | Member | Read-only license|  IT license  |
 |:------------------------|:-----:|:------:|:----------------:|:------------:|
-| Account settings        |   W   |   W    |                  |       W      |
-| Billing                 |   W   |        |                  |       W      |
-| Invitations             |   W   |   W    |                  |       W      |
-| Licenses                |   W   |   R    |                  |       W      |
-| Users                   |   W   |   R    |                  |       W      |
-| Project (create)        |   W   |   W    |                  |       W      |
-| Connections             |   W   |   W    |                  |       W      |
-| Service tokens          |   W   |        |                  |       W      |
-| Webhooks                |   W   |   W    |                  |              |
+| Account settings        |   W   |   W    |         -        |       W      |
+| Billing                 |   W   |   -    |         -        |       W      |
+| Invitations             |   W   |   W    |         -        |       W      |
+| Licenses                |   W   |   R    |         -        |       W      |
+| Users                   |   W   |   R    |         -        |       W      |
+| Project (create)        |   W   |   W    |         -        |       W      |
+| Connections             |   W   |   W    |         -        |       W      |
+| Service tokens          |   W   |   -    |         -        |       W      |
+| Webhooks                |   W   |   W    |         -        |       -      |
 
 #### Project permissions for account roles
 
 |Project-level permission | Owner | Member  | Read-only | IT license |
 |:------------------------|:-----:|:-------:|:---------:|:----------:|
-| Adapters                |   W   |    W    |    R      |             |
-| Connections             |   W   |    W    |    R      |             |
-| Credentials             |   W   |    W    |    R      |             |
-| Custom env. variables   |   W   |    W    |    R      |             |
-| Develop (IDE or dbt Cloud CLI)| W |  W    |           |             |
-| Environments            |   W   |    W    |    R      |             |
-| Jobs                    |   W   |    W    |    R      |             |
-| dbt Explorer            |   W   |    W   |    R      |             |
-| Permissions             |   W   |    R    |           |             |
-| Profile                 |   W   |    W    |    R      |             |
-| Projects                |   W   |    W    |    R      |             |
-| Repositories            |   W   |    W    |    R      |             |
-| Runs                    |   W   |    W    |    R      |             |
-| Semantic Layer Config   |   W   |    W    |    R      |             |
+| Adapters                |   W   |    W    |    R      |      -      |
+| Connections             |   W   |    W    |    R      |      -      |
+| Credentials             |   W   |    W    |    R      |      -      |
+| Custom env. variables   |   W   |    W    |    R      |      -      |
+| Develop (IDE or dbt Cloud CLI)| W |  W    |    -      |      -      |
+| Environments            |   W   |    W    |    R      |      -      |
+| Jobs                    |   W   |    W    |    R      |      -      |
+| dbt Explorer            |   W   |    W    |    R      |      -      |
+| Permissions             |   W   |    R    |    -      |      -      |
+| Profile                 |   W   |    W    |    R      |      -      |
+| Projects                |   W   |    W    |    R      |      -      |
+| Repositories            |   W   |    W    |    R      |      -      |
+| Runs                    |   W   |    W    |    R      |      -      |
+| Semantic Layer Config   |   W   |    W    |    R      |      -      |
 
 
diff --git a/website/docs/reference/resource-configs/database.md b/website/docs/reference/resource-configs/database.md
@@ -79,22 +79,19 @@ This results in the generated relation being located in the `snapshots` database
 
 <TabItem value="test" label="Tests">
 
-Configure a database in your `dbt_project.yml` file. 
+Customize the database for storing test results in your `dbt_project.yml` file.
 
-For example, to load a test into a database called `reporting` instead of the target database, you can configure it like this:
+For example, to save test results in a specific database, you can configure it like this:
 
 <File name='dbt_project.yml'>
 
 ```yml
 tests:
-  - my_not_null_test:
-      column_name: order_id
-      type: not_null
-      +database: reporting
+  +store_failures: true
+  +database: test_results
 ```
 
-This would result in the generated relation being located in the `reporting` database, so the full relation name would be `reporting.finance.my_not_null_test`.
-
+This would result in the test results being stored in the `test_results` database.
 </File>
 </TabItem>
 </Tabs>

diff --git a/website/docs/reference/snapshot-configs.md b/website/docs/reference/snapshot-configs.md
@@ -346,6 +346,7 @@ The following examples demonstrate how to configure snapshots using the `dbt_pro
         {{
             config(
               unique_key='id',
+              target_schema='snapshots',
               strategy='timestamp',
               updated_at='updated_at'
             )