Merge branch 'current' into patch-1

website/blog/2024-01-09-defer-in-development.md

@@ -12,7 +12,7 @@ date: 2024-01-09
 is_featured: true
 ---
 
-Picture this — you’ve got a massive dbt project, thousands of models chugging along, creating actionable insights for your stakeholders. A ticket comes your way — a model needs to be refactored! "No problem," you think to yourself, "I will simply make that change and test it locally!" You look at you lineage, and realize this model is many layers deep, buried underneath a long chain of tables and views.
+Picture this — you’ve got a massive dbt project, thousands of models chugging along, creating actionable insights for your stakeholders. A ticket comes your way — a model needs to be refactored! "No problem," you think to yourself, "I will simply make that change and test it locally!" You look at your lineage, and realize this model is many layers deep, buried underneath a long chain of tables and views.
 
 “OK,” you think further, “I’ll just run a `dbt build -s +my_changed_model` to make sure I have everything I need built into my dev schema and I can test my changes”. You run the command. You wait. You wait some more. You get some coffee, and completely take yourself out of your dbt development flow state. A lot of time and money down the drain to get to a point where you can *start* your work. That’s no good!
 

website/docs/best-practices/best-practice-workflows.md

@@ -39,7 +39,7 @@ Your dbt project will depend on raw data stored in your database. Since this dat
 
 :::info Using sources for raw data references
 
-As of v0.13.0, we recommend defining your raw data as [sources](/docs/build/sources), and selecting from the source rather than using the direct relation reference. Our dbt projects no longer contain any direct relation references in any models.
+We recommend defining your raw data as [sources](/docs/build/sources), and selecting from the source rather than using the direct relation reference. Our dbt projects don't contain any direct relation references in any models.
 
 :::
 

website/docs/docs/build/groups.md

@@ -7,18 +7,6 @@ keywords:
   - groups access mesh
 ---
 
-:::info New functionality
-This functionality is new in v1.5.
-:::
-
-## Related docs
-
-* [Model Access](/docs/collaborate/govern/model-access#groups)
-* [Group configuration](/reference/resource-configs/group)
-* [Group selection](/reference/node-selection/methods#the-group-method)
-
-## About groups 
-
 A group is a collection of nodes within a dbt DAG. Groups are named, and every group has an `owner`. They enable intentional collaboration within and across teams by restricting [access to private](/reference/resource-configs/access) models.
 
 Group members may include models, tests, seeds, snapshots, analyses, and metrics. (Not included: sources and exposures.) Each node may belong to only one group.
@@ -126,3 +114,9 @@ dbt.exceptions.DbtReferenceError: Parsing Error
   Node model.jaffle_shop.marketing_model attempted to reference node model.jaffle_shop.finance_model, 
   which is not allowed because the referenced node is private to the finance group.
 ```
+
+## Related docs
+
+* [Model Access](/docs/collaborate/govern/model-access#groups)
+* [Group configuration](/reference/resource-configs/group)
+* [Group selection](/reference/node-selection/methods#the-group-method)

website/docs/docs/build/materializations.md

@@ -120,7 +120,7 @@ required with incremental materializations
   * `dbt run` on materialized views corresponds to a code deployment, just like views
 * **Cons:**
   * Due to the fact that materialized views are more complex database objects, database platforms tend to have
-less configuration options available, see your database platform's docs for more details
+fewer configuration options available; see your database platform's docs for more details
   * Materialized views may not be supported by every database platform
 * **Advice:**
   * Consider materialized views for use cases where incremental models are sufficient, but you would like the data platform to manage the incremental logic and refresh.

website/docs/docs/build/project-variables.md

@@ -25,13 +25,6 @@ Jinja is not supported within the `vars` config, and all values will be interpre
 
 :::
 
-:::info New in v0.17.0
-
-The syntax for specifying vars in the `dbt_project.yml` file has changed in
-dbt v0.17.0. See the [migration guide](/docs/dbt-versions/core-upgrade)
-for more information on these changes.
-
-:::
 
 To define variables in a dbt project, add a `vars` config to your `dbt_project.yml` file.
 These `vars` can be scoped globally, or to a specific package imported in your

website/docs/docs/core/connect-data-platform/connection-profiles.md

@@ -83,11 +83,8 @@ To set up your profile, copy the correct sample profile for your warehouse into
 
 You can find more information on which values to use in your targets below.
 
-:::info Validating your warehouse credentials
+Use the [debug](/reference/dbt-jinja-functions/debug-method) command to validate your warehouse connection. Run `dbt debug` from within a dbt project to test your connection.
 
-Use the [debug](/reference/dbt-jinja-functions/debug-method) command to check whether you can successfully connect to your warehouse. Simply run `dbt debug` from within a dbt project to test your connection.
-
-:::
 
 ## Understanding targets in profiles
 

website/docs/docs/dbt-cloud-apis/schema-discovery-environment.mdx

@@ -18,13 +18,6 @@ When querying for `environment`, you can use the following arguments.
 
 <QueryArgsTable queryName="environment" useBetaAPI />
 
-:::caution
-
-dbt Labs is making changes to the Discovery API. These changes will take effect on August 15, 2023.
-
-The data type `Int` for `id` is being deprecated and will be replaced with `BigInt`. When the time comes, you will need to update your API call accordingly to avoid errors.
-:::
-
 ### Example queries
 
 You can use your production environment's `id`:

website/docs/docs/dbt-versions/core-upgrade/00-upgrading-to-v1.7.md

@@ -5,10 +5,6 @@ description: New features and changes in dbt Core v1.7
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ## Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/8aaed0e29f9560bc53d9d3e88325a9597318e375/CHANGELOG.md)

website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.6.md

@@ -5,10 +5,6 @@ id: "upgrading-to-v1.6"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 dbt Core v1.6 has three significant areas of focus:
 1. Next milestone of [multi-project deployments](https://github.com/dbt-labs/dbt-core/discussions/6725): improvements to contracts, groups/access, versions; and building blocks for cross-project `ref`
 1. Semantic layer re-launch: dbt Core and [MetricFlow](https://docs.getdbt.com/docs/build/about-metricflow) integration

website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.5.md

@@ -5,10 +5,6 @@ id: "upgrading-to-v1.5"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 dbt Core v1.5 is a feature release, with two significant additions:
 1. [**Model governance**](/docs/collaborate/govern/about-model-governance) — access, contracts, versions — the first phase of [multi-project deployments](https://github.com/dbt-labs/dbt-core/discussions/6725)
 2. A Python entry point for [**programmatic invocations**](/reference/programmatic-invocations), at parity with the CLI

website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-dbt-utils-v1.0.md

@@ -3,10 +3,6 @@ title: "Upgrading to dbt utils v1.0"
 description: New features and breaking changes to consider as you upgrade to dbt utils v1.0.
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 # Upgrading to dbt utils v1.0
 
 For the first time, [dbt utils](https://hub.getdbt.com/dbt-labs/dbt_utils/latest/) is crossing the major version boundary. From [last month’s blog post](https://www.getdbt.com/blog/announcing-dbt-v1.3-and-utils/): 

website/docs/docs/dbt-versions/core-upgrade/04-upgrading-to-v1.4.md

@@ -5,10 +5,6 @@ id: "upgrading-to-v1.4"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md)

website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.3.md

@@ -5,10 +5,6 @@ id: "upgrading-to-v1.3"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.3.latest/CHANGELOG.md)

website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.2.md

@@ -5,10 +5,6 @@ id: "upgrading-to-v1.2"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.2.latest/CHANGELOG.md)

website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.1.md

@@ -5,10 +5,6 @@ id: "upgrading-to-v1.1"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.1.latest/CHANGELOG.md)

website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.0.md

@@ -5,9 +5,6 @@ id: "upgrading-to-v1.0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
 
 ### Resources
 

website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v0.21.md

@@ -5,10 +5,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 
 :::caution Unsupported version
 dbt Core v0.21 has reached the end of critical support. No new patch versions will be released, and it will stop running in dbt Cloud on June 30, 2022. Read ["About dbt Core versions"](/docs/dbt-versions/core) for more details.

website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v0.20.md

@@ -4,10 +4,6 @@ id: "upgrading-to-v0.20"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 :::caution Unsupported version
 dbt Core v0.20 has reached the end of critical support. No new patch versions will be released, and it will stop running in dbt Cloud on June 30, 2022. Read ["About dbt Core versions"](/docs/dbt-versions/core) for more details.
 :::

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-11-0.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-11-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ## Schema.yml v2 syntax
 dbt v0.11.0 adds an auto-generated docs site to your dbt project. To make effective use of the documentation site, you'll need to use the new "version 2" schema.yml syntax. For a full explanation of the version 2 syntax, check out the [schema.yml Files](/reference/configs-and-properties) section of the documentation.
 

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-12-0.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-12-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ## End of support
 
 Support for the `repositories:` block in `dbt_project.yml` (deprecated in 0.10.0) was removed.

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-13-0.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-13-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ## Breaking changes
 
 ### on-run-start and on-run-end

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-0.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-14-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 This guide outlines migration instructions for:
 
 1. [Upgrading archives to snapshots](#upgrading-to-snapshot-blocks)

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-1.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-14-1"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 The dbt v0.14.1 release _does not_ contain any breaking code changes for users upgrading from v0.14.0. If you are upgrading from a version less than 0.14.0, consult the [Upgrading to 0.14.0](upgrading-to-0-14-0) migration guide. The following section contains important information for users of the `check` strategy on Snowflake and BigQuery. Action may be required in your database.
 
 ## Changes to the Snapshot "check" algorithm

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-15-0.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-15-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 The dbt v0.15.0 release contains a handful of breaking code changes for users upgrading from v0.14.0.
 
 

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-16-0.md

@@ -4,10 +4,6 @@ id: "upgrading-to-0-16-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 dbt v0.16.0 contains many new features, bug fixes, and improvements. This guide
 covers all of the important information to consider when upgrading from an earlier
 version of dbt to 0.16.0.

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-17-0.md

@@ -5,10 +5,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 dbt v0.17.0 makes compilation more consistent, improves performance, and fixes a number of bugs.
 
 ## Articles:
@@ -252,8 +248,8 @@ BigQuery:
 
 **Core**
 - [`path:` selectors](/reference/node-selection/methods#the-path-method)
-- [`--fail-fast`](/reference/commands/run#failing-fast)
-- [as_text Jinja filter](/reference/dbt-jinja-functions/as_text)
+- [`--fail-fast` command](/reference/commands/run#failing-fast)
+- `as_text` Jinja filter: removed this defunct filter
 - [accessing nodes in the `graph` object](/reference/dbt-jinja-functions/graph)
 - [persist_docs](/reference/resource-configs/persist_docs)
 - [source properties](reference/source-properties)

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-18-0.md

@@ -4,10 +4,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/dev/marian-anderson/CHANGELOG.md)

website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-19-0.md

@@ -4,10 +4,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Discourse](https://discourse.getdbt.com/t/1951)

website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md

@@ -8,7 +8,7 @@ tags: [Oct-2023]
 ---
 
 :::important
-If you're using the legacy Semantic Layer, we **highly** recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher and [migrate](/guides/sl-migration) to the latest Semantic Layer.
+If you're using the legacy Semantic Layer, we _highly_ recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher and [migrate](/guides/sl-migration) to the latest Semantic Layer.
 :::
 
 dbt Labs is thrilled to announce that the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl) is now generally available. It offers consistent data organization, improved governance, reduced costs, enhanced efficiency, and accessible data for better decision-making and collaboration across organizations.

website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md

@@ -8,7 +8,7 @@ sidebar_position: 7
 ---
 
 :::important
-If you're using the legacy Semantic Layer, we **highly** recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. To migrate to the new Semantic Layer, refer to the dedicated [migration guide](/guides/sl-migration) for more info.
+If you're using the legacy Semantic Layer, we _highly_ recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. To migrate to the new Semantic Layer, refer to the dedicated [migration guide](/guides/sl-migration) for more info.
 :::
 
 dbt Labs are thrilled to announce the re-release of the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl), now available in [public beta](#public-beta). It aims to bring the best of modeling and semantics to downstream applications by introducing:

website/docs/docs/dbt-versions/upgrade-core-in-cloud.md

@@ -134,12 +134,6 @@ If you believe your project might be affected, read more details in the migratio
 <br></br>
 <div>
 
-:::info Important   
-
-If you have not already, you must add `config-version: 2` to your dbt_project.yml file.
-See **Upgrading to v0.17.latest from v0.16** below for more details.
-
-:::
 </div>
 
 

website/docs/faqs/API/rotate-token.md

@@ -36,15 +36,15 @@ curl --location --request POST 'https://YOUR_ACCESS_URL/api/v2/users/YOUR_USER_I
 * Find your `YOUR_CURRENT_TOKEN` by going to **Profile Settings** -> **API Access** and copying the API key.
 * Find [`YOUR_ACCESS_URL`](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan.
 
-:::info Example
+Example:
 
 If `YOUR_USER_ID` = `123`, `YOUR_CURRENT_TOKEN` = `abcf9g`, and your `ACCESS_URL` = `cloud.getdbt.com`, then your curl request will be:
 
 ```
 curl --location --request POST 'https://cloud.getdbt.com/api/v2/users/123/apikey/' \
 --header 'Authorization: Token abcf9g'
 ```
-:::
+
 
 2. Find the new key in the API response or in dbt Cloud.