Merge branch 'current' into nfiann-guides

website/docs/docs/cloud/about-cloud-develop-defer.md

@@ -13,11 +13,13 @@ Both the dbt Cloud IDE and the dbt Cloud CLI enable users to natively defer to p
 
 <Lightbox src src="/img/docs/reference/defer-diagram.png" width="50%" title="Use 'defer' to modify end-of-pipeline models by pointing to production models, instead of running everything upstream." />
 
-By default, dbt follows these rules:
+When using `--defer`, dbt Cloud will follow this order of execution for resolving the `{{ ref() }}` functions.
 
-- dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment.
-- If a development version of a deferred model exists, dbt preferentially uses the development database location when resolving the reference.
-- Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag overrides the default behavior and _always_ resolve refs using production metadata, regardless of the presence of a development relation.
+1. If a development version of a deferred relation exists, dbt preferentially uses the development database location when resolving the reference.
+2. If a development version doesn't exist, dbt uses the staging locations of parent relations based on metadata from the staging environment.
+3. If both a development and staging version doesn't exist, dbt uses the production locations of parent relations based on metadata from the production environment.
+
+**Note:** Passing the `--favor-state` flag will always resolve refs using production metadata, regardless of the presence of a development relation, skipping step #1.
 
 For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle.
 

website/docs/docs/deploy/job-notifications.md

@@ -52,6 +52,8 @@ You can receive email alerts about jobs by configuring the dbt Cloud email notif
 You can receive Slack alerts about jobs by setting up the Slack integration and then configuring the dbt Cloud Slack notification settings. dbt Cloud integrates with Slack via OAuth to ensure secure authentication.
 
 :::note 
+Virtual Private Cloud (VPC) admins must [contact support](mailto:[email protected]) to complete the Slack integration.
+
 If there has been a change in user roles or Slack permissions where you no longer have access to edit a configured Slack channel, please [contact support](mailto:[email protected]) for assistance. 
 :::
 

website/docs/reference/data-test-configs.md

@@ -275,3 +275,24 @@ tests:
 ```
 
 </File>
+
+#### Specify custom configurations for generic data tests
+
+Beginning in dbt v1.9, you can use any custom config key to specify custom configurations for data tests. For example, the following specifies the `snowflake_warehouse` custom config that dbt should use when executing the `accepted_values` data test:
+
+```yml
+
+models:
+  - name: my_model
+    columns:
+      - name: color
+        tests:
+          - accepted_values:
+              values: ['blue', 'red']
+              config:
+                severity: warn
+                snowflake_warehouse: my_warehouse
+
+```
+
+Given the config, the data test runs on a different Snowflake virtual warehouse than the one in your default connection to enable better price-performance with a different warehouse size or more granular cost allocation and visibility.

website/docs/reference/snapshot-configs.md

@@ -198,8 +198,8 @@ snapshots:
       [enabled](/reference/resource-configs/enabled): true | false
       [tags](/reference/resource-configs/tags): <string> | [<string>]
       [alias](/reference/resource-configs/alias): <string>
-      [pre-hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
-      [post-hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
+      [pre_hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
+      [post_hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
       [persist_docs](/reference/resource-configs/persist_docs): {<dict>}
       [grants](/reference/resource-configs/grants): {<dictionary>}
 ```
@@ -221,8 +221,8 @@ snapshots:
       [enabled](/reference/resource-configs/enabled): true | false
       [tags](/reference/resource-configs/tags): <string> | [<string>]
       [alias](/reference/resource-configs/alias): <string>
-      [pre-hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
-      [post-hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
+      [pre_hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
+      [post_hook](/reference/resource-configs/pre-hook-post-hook): <sql-statement> | [<sql-statement>]
       [persist_docs](/reference/resource-configs/persist_docs): {<dict>}
       [grants](/reference/resource-configs/grants): {<dictionary>}
 ```

website/src/css/custom.css

@@ -2112,3 +2112,35 @@ h2.anchor.clicked a.hash-link:before {
     flex-direction: column;
   }
 }
+
+.markdown table th,
+.markdown table td {
+    padding: 8px;
+    border: 1px solid var(--table-border-color);
+    word-wrap: break-word;
+    white-space: normal;
+    text-align: left;
+}
+
+table th {
+  background-color: #ED7254; /* Table header background color */
+}
+
+:root {
+    --table-border-color: #000000; /* Light mode table border color */
+}
+
+/* Dark mode border */
+[data-theme="dark"] {
+    --table-border-color: #ddd; /* Dark mode table border color */
+}
+table th {
+  color: #ffffff; /* White text on lighter background */
+  font-weight: bold;
+}
+
+/* Dark mode table header text */
+[data-theme='dark'] table th {
+  color: #000000; /* Black text on darker background */
+  font-weight: bold;
+}