Merge pull request #238 from dbt-labs/repo-sync

REPO SYNC - Public to Private

website/docs/docs/collaborate/govern/project-dependencies.md

@@ -7,6 +7,12 @@ description: "Reference public models across dbt projects"
 
 :::caution Closed Beta - dbt Cloud Enterprise
 "Project" dependencies and cross-project `ref` are features of dbt Cloud Enterprise, currently in Closed Beta. To access these features while they are in beta, please contact your account team at dbt Labs.
+
+**Prerequisites:** In order to add project dependencies and resolve cross-project `ref`, you must:
+- Have the feature enabled (speak to your account team)
+- Use dbt v1.6 for **both** the upstream ("producer") project and the downstream ("consumer") project.
+- Have a deployment environment in the upstream ("producer") project [that is set to be your production environment](/docs/deploy/deploy-environments#set-as-production-environment-beta)
+- Have a successful run of the upstream ("producer") project
 :::
 
 For a long time, dbt has supported code reuse and extension by installing other projects as [packages](/docs/build/packages). When you install another project as a package, you are pulling in its full source code, and adding it to your own. This enables you to call macros and run models defined in that other project.

website/docs/docs/verified-adapters.md

@@ -1,18 +1,19 @@
 ---
 title: "Verified adapters"
 id: "verified-adapters"
+hide_table_of_contents: true
 ---
 
 
-The dbt Labs has a rigorous verified adapter program which provides reassurance to users about which adapters can be trusted to use in production, has been tested, and is actively maintained and updated. The process covers aspects of development, documentation, user experience, and maintenance.
+The dbt Labs has a rigorous verified adapter program that provides reassurance to users about which adapters can be trusted to use in production, has been tested, and is actively maintained and updated. The process covers development, documentation, user experience, and maintenance aspects.
 
 These adapters then earn a "Verified" status so that users can have a certain level of trust and expectation when they use them. The adapters also have maintainers and we recommend using the adapter's verification status to determine its quality and health.
 
 The verification process serves as the on-ramp to integration with dbt Cloud. As such, we restrict applicants to data platform vendors with whom we are already engaged.
 
 To learn more, see [Verifying a new adapter](/guides/dbt-ecosystem/adapter-development/7-verifying-a-new-adapter).
 
-Here's the list of the verified data platforms that can connect to dbt and its latest version.
+Here are the verified data platforms that connect to dbt and its latest version.
 
 import AdaptersVerified from '/snippets/_adapters-verified.md';
 

website/docs/reference/node-selection/methods.md

@@ -47,13 +47,19 @@ The `source` method is used to select models that select from a specified [sourc
   ```
 
 ### The "resource_type" method
-Use the `resource_type` method to select nodes of a particular type (`model`, `source`, `exposure`, etc). This is similar to the `--resource-type` flag used by the [`dbt ls` command](/reference/commands/list).
+Use the `resource_type` method to select nodes of a particular type (`model`, `test`, `exposure`, and so on). This is similar to the `--resource-type` flag used by the [`dbt ls` command](/reference/commands/list).
 
   ```bash
   $ dbt build --select resource_type:exposure    # build all resources upstream of exposures
   $ dbt list --select resource_type:test    # list all tests in your project
   ```
 
+Note: This method doesn't work for sources, so use the [`--resource-type`](/reference/commands/list) option of the list command instead:
+
+  ```bash
+  $ dbt list --resource-type source
+  ```
+
 ### The "path" method
 The `path` method is used to select models/sources defined at or under a specific path.
 Model definitions are in SQL/Python files (not YAML), and source definitions are in YAML files.

website/docs/reference/resource-configs/docs.md

@@ -28,6 +28,7 @@ models:
   - name: model_name
     docs:
       show: true | false
+      node_color: "black"
 
 ```
 
@@ -113,13 +114,13 @@ macros:
 ```
 
 </File>
-
+Also refer to [macro properties](/reference/macro-properties).
 </TabItem>
 
 </Tabs>
 
 ## Definition
-The docs field can be used to provide documentation-specific configuration to models. The only currently supported docs attribute is shown, which controls whether or not models are shown in the auto-generated documentation website.
+The docs field can be used to provide documentation-specific configuration to models. It supports the doc attribute `show`, which controls whether or not models are shown in the auto-generated documentation website. It also supports `node_color` for some node types.
 
 **Note:** hidden models will still appear in the dbt DAG visualization but will be identified as "hidden.”
 
@@ -167,7 +168,7 @@ models:
 
 ## Custom node colors
 
-The `docs` attribute now supports `node_color` to customize the node color in the DAG within dbt docs. You can define node colors in the files below and apply overrides where needed.
+The `docs` attribute now supports `node_color` to customize the display color of some node types in the DAG within dbt docs. You can define node colors in the files below and apply overrides where needed.
 
 `node_color` hiearchy:
 
@@ -176,7 +177,7 @@ The `docs` attribute now supports `node_color` to customize the node color in th
 
 ## Examples
 
-Add custom node colors to models within subdirectories based on hex codes or a plain color name.
+Add custom `node_colors` to models that support it within subdirectories based on hex codes or a plain color name.
 
 ![Example](../../../../website/static/img/node_color_example.png)
 

website/snippets/_sl-plan-info.md

@@ -1 +1 @@
-<span>To define and query metrics with the {props.product}, you must be on a <a href="https://www.getdbt.com/pricing/">{props.plan}</a>  multi-tenant plan, <a href="https://docs.getdbt.com/docs/cloud/about-cloud/regions-ip-addresses" target="_self">{props.instance}</a> (Additional region support coming soon).<br /><br /> The re-released dbt Semantic Layer is available on dbt v1.6 or higher. dbt Core users can use the <a href="https://docs.getdbt.com/docs/build/metricflow-cli">MetricFlow CLI</a> to define metrics in their local project, but won't be able dynamically query them with integrated tools.</span><br /><br />
+<span>To define and query metrics with the {props.product}, you must be on a <a href="https://www.getdbt.com/pricing/">{props.plan}</a>  multi-tenant plan, <a href="https://docs.getdbt.com/docs/cloud/about-cloud/regions-ip-addresses" target="_self">{props.instance}</a> (Additional region support coming soon).<br /><br /> The re-released dbt Semantic Layer is available on dbt v1.6 or higher. dbt Core users can use the <a href="https://docs.getdbt.com/docs/build/metricflow-cli">MetricFlow CLI</a> to define metrics in their local project, but won't be able to dynamically query them with integrated tools.</span><br /><br />