From a3e8e2a484f6a01c9640adef549668ffa5e80b8c Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 8 Jan 2024 16:44:15 -0500 Subject: [PATCH 01/25] Updating notices across docs --- .../best-practices/best-practice-workflows.md | 2 +- website/docs/docs/build/groups.md | 18 ++++++------------ website/docs/docs/build/project-variables.md | 7 ------- .../connection-profiles.md | 5 +---- .../schema-discovery-environment.mdx | 7 ------- .../core-upgrade/00-upgrading-to-v1.7.md | 4 ---- .../core-upgrade/01-upgrading-to-v1.6.md | 4 ---- .../core-upgrade/02-upgrading-to-v1.5.md | 4 ---- .../03-upgrading-to-dbt-utils-v1.0.md | 4 ---- .../core-upgrade/04-upgrading-to-v1.4.md | 4 ---- .../core-upgrade/05-upgrading-to-v1.3.md | 4 ---- .../core-upgrade/06-upgrading-to-v1.2.md | 4 ---- .../core-upgrade/07-upgrading-to-v1.1.md | 4 ---- .../core-upgrade/08-upgrading-to-v1.0.md | 3 --- .../core-upgrade/09-upgrading-to-v0.21.md | 4 ---- .../core-upgrade/10-upgrading-to-v0.20.md | 4 ---- .../11-Older versions/upgrading-to-0-11-0.md | 4 ---- .../11-Older versions/upgrading-to-0-12-0.md | 4 ---- .../11-Older versions/upgrading-to-0-13-0.md | 4 ---- .../11-Older versions/upgrading-to-0-14-0.md | 4 ---- .../11-Older versions/upgrading-to-0-14-1.md | 4 ---- .../11-Older versions/upgrading-to-0-15-0.md | 4 ---- .../11-Older versions/upgrading-to-0-16-0.md | 4 ---- .../11-Older versions/upgrading-to-0-17-0.md | 4 ---- .../11-Older versions/upgrading-to-0-18-0.md | 4 ---- .../11-Older versions/upgrading-to-0-19-0.md | 4 ---- .../release-notes/76-Oct-2023/sl-ga.md | 2 +- .../78-Aug-2023/sl-revamp-beta.md | 2 +- .../docs/dbt-versions/upgrade-core-in-cloud.md | 6 ------ website/docs/faqs/API/rotate-token.md | 4 ++-- .../Accounts/cloud-upgrade-instructions.md | 6 ++++-- website/docs/guides/adapter-creation.md | 6 ------ website/docs/guides/bigquery-qs.md | 4 +--- website/docs/guides/databricks-qs.md | 4 +--- website/docs/guides/debug-schema-names.md | 9 ++------- ...tabricks-workflows-to-run-dbt-cloud-jobs.md | 13 +++++-------- website/docs/guides/redshift-qs.md | 4 ---- .../guides/sl-partner-integration-guide.md | 3 --- website/docs/guides/snowflake-qs.md | 6 ++---- website/docs/guides/starburst-galaxy-qs.md | 5 +---- .../reference/dbt-jinja-functions/as_text.md | 13 +++++++------ .../reference/dbt-jinja-functions/env_var.md | 5 +++-- website/docs/reference/dbt_project.yml.md | 7 ++----- .../docs/reference/node-selection/methods.md | 3 --- .../reference/project-configs/clean-targets.md | 5 +++-- .../reference/project-configs/docs-paths.md | 9 ++++----- .../project-configs/require-dbt-version.md | 13 ++++--------- .../reference/resource-configs/contract.md | 16 ++++++---------- .../reference/resource-configs/delimiter.md | 9 ++------- .../docs/reference/resource-configs/group.md | 4 ---- .../reference/resource-properties/database.md | 5 +---- .../reference/resource-properties/schema.md | 4 +--- .../aggregate-functions/sql-avg.md | 6 ++---- .../aggregate-functions/sql-count.md | 5 ++--- .../aggregate-functions/sql-max.md | 6 ++---- .../aggregate-functions/sql-min.md | 6 ++---- .../aggregate-functions/sql-round.md | 5 +---- .../aggregate-functions/sql-sum.md | 6 ++---- website/docs/terms/data-extraction.md | 2 +- website/docs/terms/table.md | 3 --- website/snippets/_cloud-environments-info.md | 14 ++++---------- website/snippets/_upgrade-move.md | 5 ----- .../snippets/available-prerelease-banner.md | 7 ------- website/snippets/quickstarts/schedule-a-job.md | 4 ++-- 64 files changed, 79 insertions(+), 279 deletions(-) delete mode 100644 website/snippets/_upgrade-move.md delete mode 100644 website/snippets/available-prerelease-banner.md diff --git a/website/docs/best-practices/best-practice-workflows.md b/website/docs/best-practices/best-practice-workflows.md index 9b79c244901..4381906361e 100644 --- a/website/docs/best-practices/best-practice-workflows.md +++ b/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. ::: diff --git a/website/docs/docs/build/groups.md b/website/docs/docs/build/groups.md index d4fda045277..62c4e4493d3 100644 --- a/website/docs/docs/build/groups.md +++ b/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) \ No newline at end of file diff --git a/website/docs/docs/build/project-variables.md b/website/docs/docs/build/project-variables.md index 59d6be49b17..a328731c7d4 100644 --- a/website/docs/docs/build/project-variables.md +++ b/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 diff --git a/website/docs/docs/core/connect-data-platform/connection-profiles.md b/website/docs/docs/core/connect-data-platform/connection-profiles.md index 8088ff1dfa7..32e60c8cc18 100644 --- a/website/docs/docs/core/connect-data-platform/connection-profiles.md +++ b/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 diff --git a/website/docs/docs/dbt-cloud-apis/schema-discovery-environment.mdx b/website/docs/docs/dbt-cloud-apis/schema-discovery-environment.mdx index a82bba6576d..a89d8f31962 100644 --- a/website/docs/docs/dbt-cloud-apis/schema-discovery-environment.mdx +++ b/website/docs/docs/dbt-cloud-apis/schema-discovery-environment.mdx @@ -18,13 +18,6 @@ When querying for `environment`, you can use the following arguments. -:::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`: diff --git a/website/docs/docs/dbt-versions/core-upgrade/00-upgrading-to-v1.7.md b/website/docs/docs/dbt-versions/core-upgrade/00-upgrading-to-v1.7.md index af098860e6f..1f40aaa9f40 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/00-upgrading-to-v1.7.md +++ b/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'; - - - ## Resources - [Changelog](https://github.com/dbt-labs/dbt-core/blob/8aaed0e29f9560bc53d9d3e88325a9597318e375/CHANGELOG.md) diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.6.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.6.md index f1f7a77e1e1..a70f220edc8 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.6.md +++ b/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'; - - - 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 diff --git a/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.5.md b/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.5.md index e739caa477a..589ac162088 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.5.md +++ b/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'; - - - 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 diff --git a/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-dbt-utils-v1.0.md b/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-dbt-utils-v1.0.md index 229a54627fc..a8bb960c37d 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/03-upgrading-to-dbt-utils-v1.0.md +++ b/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'; - - - # 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/): diff --git a/website/docs/docs/dbt-versions/core-upgrade/04-upgrading-to-v1.4.md b/website/docs/docs/dbt-versions/core-upgrade/04-upgrading-to-v1.4.md index 240f0b86de3..41e19956690 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/04-upgrading-to-v1.4.md +++ b/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'; - - - ### Resources - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md) diff --git a/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.3.md b/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.3.md index 5a381b16928..7febb0bade9 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/05-upgrading-to-v1.3.md +++ b/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'; - - - ### Resources - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.3.latest/CHANGELOG.md) diff --git a/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.2.md b/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.2.md index cd75e7f411b..17e62c90b43 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.2.md +++ b/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'; - - - ### Resources - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.2.latest/CHANGELOG.md) diff --git a/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.1.md b/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.1.md index 868f3c7ed04..aee3413e1ad 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/07-upgrading-to-v1.1.md +++ b/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'; - - - ### Resources - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.1.latest/CHANGELOG.md) diff --git a/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.0.md b/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.0.md index 0ea66980874..9cbfae50831 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/08-upgrading-to-v1.0.md +++ b/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'; - - ### Resources diff --git a/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v0.21.md b/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v0.21.md index d5b429132cd..5575b0cc2af 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/09-upgrading-to-v0.21.md +++ b/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'; - - - :::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. diff --git a/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v0.20.md b/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v0.20.md index be6054087b3..d95b8d8bacd 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/10-upgrading-to-v0.20.md +++ b/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'; - - - :::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. ::: diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-11-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-11-0.md index e91dde4c923..27c0456660f 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-11-0.md +++ b/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'; - - - ## 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. diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-12-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-12-0.md index b3d4e9d9bcb..a95ec3b11bd 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-12-0.md +++ b/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'; - - - ## End of support Support for the `repositories:` block in `dbt_project.yml` (deprecated in 0.10.0) was removed. diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-13-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-13-0.md index bb15d1a73b0..9875eb3c346 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-13-0.md +++ b/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'; - - - ## Breaking changes ### on-run-start and on-run-end diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-0.md index 48aa14a42e5..21cfbe8d3b5 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-0.md +++ b/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'; - - - This guide outlines migration instructions for: 1. [Upgrading archives to snapshots](#upgrading-to-snapshot-blocks) diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-1.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-1.md index 215385acf0f..559775644cd 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-14-1.md +++ b/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'; - - - 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 diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-15-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-15-0.md index 5eba212590f..7db64f5940f 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-15-0.md +++ b/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'; - - - The dbt v0.15.0 release contains a handful of breaking code changes for users upgrading from v0.14.0. diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-16-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-16-0.md index 076e6fc4e88..d6fc6f9f49a 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-16-0.md +++ b/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'; - - - 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. diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-17-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-17-0.md index 5b863777df9..adc6747310c 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-17-0.md +++ b/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'; - - - dbt v0.17.0 makes compilation more consistent, improves performance, and fixes a number of bugs. ## Articles: diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-18-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-18-0.md index 545bfd41ac6..f14fd03a534 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-18-0.md +++ b/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'; - - - ### Resources - [Changelog](https://github.com/dbt-labs/dbt-core/blob/dev/marian-anderson/CHANGELOG.md) diff --git a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-19-0.md b/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-19-0.md index db825d8af9c..af978f9c6a9 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-19-0.md +++ b/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'; - - - ### Resources - [Discourse](https://discourse.getdbt.com/t/1951) diff --git a/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md b/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md index a81abec5d42..a1b59aa6ec1 100644 --- a/website/docs/docs/dbt-versions/release-notes/76-Oct-2023/sl-ga.md +++ b/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. diff --git a/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md b/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md index f44fd57aa4a..ac8e286c783 100644 --- a/website/docs/docs/dbt-versions/release-notes/78-Aug-2023/sl-revamp-beta.md +++ b/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: diff --git a/website/docs/docs/dbt-versions/upgrade-core-in-cloud.md b/website/docs/docs/dbt-versions/upgrade-core-in-cloud.md index e46294029ec..052611f66e6 100644 --- a/website/docs/docs/dbt-versions/upgrade-core-in-cloud.md +++ b/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

-:::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. - -:::
diff --git a/website/docs/faqs/API/rotate-token.md b/website/docs/faqs/API/rotate-token.md index 144c834ea8a..4470de72d5a 100644 --- a/website/docs/faqs/API/rotate-token.md +++ b/website/docs/faqs/API/rotate-token.md @@ -36,7 +36,7 @@ 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: @@ -44,7 +44,7 @@ If `YOUR_USER_ID` = `123`, `YOUR_CURRENT_TOKEN` = `abcf9g`, and your `ACCESS_URL 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. diff --git a/website/docs/faqs/Accounts/cloud-upgrade-instructions.md b/website/docs/faqs/Accounts/cloud-upgrade-instructions.md index f8daf393f9b..c3ccade3e4a 100644 --- a/website/docs/faqs/Accounts/cloud-upgrade-instructions.md +++ b/website/docs/faqs/Accounts/cloud-upgrade-instructions.md @@ -6,11 +6,13 @@ description: "Instructions for upgrading a dbt Cloud account after the trial end dbt Cloud offers [several plans](https://www.getdbt.com/pricing/) with different features that meet your needs. This document is for dbt Cloud admins and explains how to select a plan in order to continue using dbt Cloud. -:::tip Before you begin +## Prerequisites + +Before you begin: - You **_must_** be part of the [Owner](/docs/cloud/manage-access/self-service-permissions) user group to make billing changes. Users not included in this group will not see these options. - All amounts shown in dbt Cloud are in U.S. Dollars (USD) - When your trial expires, your account's default plan enrollment will be a Team plan. -::: + ## Select a plan diff --git a/website/docs/guides/adapter-creation.md b/website/docs/guides/adapter-creation.md index 8bf082b04a0..28e0e8253ad 100644 --- a/website/docs/guides/adapter-creation.md +++ b/website/docs/guides/adapter-creation.md @@ -566,12 +566,6 @@ It should be noted that both of these files are included in the bootstrapped out ## Test your adapter -:::info - -Previously, we offered a packaged suite of tests for dbt adapter functionality: [`pytest-dbt-adapter`](https://github.com/dbt-labs/dbt-adapter-tests). We are deprecating that suite, in favor of the newer testing framework outlined in this document. - -::: - This document has two sections: 1. Refer to "About the testing framework" for a description of the standard framework that we maintain for using pytest together with dbt. It includes an example that shows the anatomy of a simple test case. diff --git a/website/docs/guides/bigquery-qs.md b/website/docs/guides/bigquery-qs.md index 9cf2447fa52..8ef97df00e9 100644 --- a/website/docs/guides/bigquery-qs.md +++ b/website/docs/guides/bigquery-qs.md @@ -21,10 +21,8 @@ In this quickstart guide, you'll learn how to use dbt Cloud with BigQuery. It wi - Document your models. - Schedule a job to run. -:::tip Videos for you -You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. -::: +You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. ### Prerequisites​ diff --git a/website/docs/guides/databricks-qs.md b/website/docs/guides/databricks-qs.md index 5a0c5536e7f..a2e08e004ed 100644 --- a/website/docs/guides/databricks-qs.md +++ b/website/docs/guides/databricks-qs.md @@ -19,10 +19,8 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Databricks. It - Document your models. - Schedule a job to run. -:::tip Videos for you -You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. -::: +You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. ### Prerequisites​ diff --git a/website/docs/guides/debug-schema-names.md b/website/docs/guides/debug-schema-names.md index c7bf1a195b1..94e1df673b8 100644 --- a/website/docs/guides/debug-schema-names.md +++ b/website/docs/guides/debug-schema-names.md @@ -14,11 +14,8 @@ recently_updated: true ## Introduction -If a model uses the [`schema` config](/reference/resource-properties/schema) but builds under an unexpected schema, here are some steps for debugging the issue. +If a model uses the [`schema` config](/reference/resource-properties/schema) but builds under an unexpected schema, here are some steps for debugging the issue. The full explanation on custom schemas can be found [here](/docs/build/custom-schemas). -:::info -The full explanation on custom schemas can be found [here](/docs/build/custom-schemas). -::: You can also follow along via this video: @@ -94,9 +91,7 @@ Now, re-read through the logic of your `generate_schema_name` macro, and mentall You should find that the schema dbt is constructing for your model matches the output of your `generate_schema_name` macro. -:::info -Note that snapshots do not follow this behavior, check out the docs on [target_schema](/reference/resource-configs/target_schema) instead. -::: +**Note:** Snapshots do not follow this behavior, check out the docs on [target_schema](/reference/resource-configs/target_schema) instead. ## Adjust as necessary diff --git a/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md b/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md index cb3a6804247..ae10cd8f521 100644 --- a/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md +++ b/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md @@ -128,15 +128,14 @@ if __name__ == '__main__': 4. Replace **``** and **``** with the correct values of your environment and [Access URL](/docs/cloud/about-cloud/regions-ip-addresses) for your region and plan. -:::tip - To find these values, navigate to **dbt Cloud**, select **Deploy -> Jobs**. Select the Job you want to run and copy the URL. For example: `https://cloud.getdbt.com/deploy/000000/projects/111111/jobs/222222` -and therefore valid code would be: + * To find these values, navigate to **dbt Cloud**, select **Deploy -> Jobs**. Select the Job you want to run and copy the URL. For example: `https://cloud.getdbt.com/deploy/000000/projects/111111/jobs/222222` + and therefore valid code would be: - # Your URL is structured https:///deploy//projects//jobs/ + Your URL is structured https:///deploy//projects//jobs/ account_id = 000000 job_id = 222222 base_url = "cloud.getdbt.com" -::: + 5. Run the Notebook. It will fail, but you should see **a `job_id` widget** at the top of your notebook. @@ -161,9 +160,7 @@ DbtJobRunStatus.RUNNING DbtJobRunStatus.SUCCESS ``` -:::note -You can cancel the job from dbt Cloud if necessary. -::: +**Note:** You can cancel the job from dbt Cloud if necessary. ## Configure the workflows to run the dbt Cloud jobs diff --git a/website/docs/guides/redshift-qs.md b/website/docs/guides/redshift-qs.md index 890be27e50a..b24d04fc0b3 100644 --- a/website/docs/guides/redshift-qs.md +++ b/website/docs/guides/redshift-qs.md @@ -18,12 +18,8 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Redshift. It wi - Document your models - Schedule a job to run - -:::tip Videos for you You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. -::: - ### Prerequisites - You have a [dbt Cloud account](https://www.getdbt.com/signup/). diff --git a/website/docs/guides/sl-partner-integration-guide.md b/website/docs/guides/sl-partner-integration-guide.md index 61d558f504d..7eb158a2c85 100644 --- a/website/docs/guides/sl-partner-integration-guide.md +++ b/website/docs/guides/sl-partner-integration-guide.md @@ -15,10 +15,7 @@ recently_updated: true To fit your tool within the world of the Semantic Layer, dbt Labs offers some best practice recommendations for how to expose metrics and allow users to interact with them seamlessly. -:::note This is an evolving guide that is meant to provide recommendations based on our experience. If you have any feedback, we'd love to hear it! -::: - ### Prerequisites diff --git a/website/docs/guides/snowflake-qs.md b/website/docs/guides/snowflake-qs.md index 5b4f9e3e2be..2b6a00bcd68 100644 --- a/website/docs/guides/snowflake-qs.md +++ b/website/docs/guides/snowflake-qs.md @@ -21,11 +21,9 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Snowflake. It w Snowflake also provides a quickstart for you to learn how to use dbt Cloud. It makes use of a different public dataset (Knoema Economy Data Atlas) than what's shown in this guide. For more information, refer to [Accelerating Data Teams with dbt Cloud & Snowflake](https://quickstarts.snowflake.com/guide/accelerating_data_teams_with_snowflake_and_dbt_cloud_hands_on_lab/) in the Snowflake docs. -:::tip Videos for you -You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. -You can also watch the [YouTube video on dbt and Snowflake](https://www.youtube.com/watch?v=kbCkwhySV_I&list=PL0QYlrC86xQm7CoOH6RS7hcgLnd3OQioG). -::: +Check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free and the [YouTube video on dbt and Snowflake](https://www.youtube.com/watch?v=kbCkwhySV_I&list=PL0QYlrC86xQm7CoOH6RS7hcgLnd3OQioG) if you're interested in course learning with videos. + ### Prerequisites​ diff --git a/website/docs/guides/starburst-galaxy-qs.md b/website/docs/guides/starburst-galaxy-qs.md index 1822c83fa90..e5c71810d0f 100644 --- a/website/docs/guides/starburst-galaxy-qs.md +++ b/website/docs/guides/starburst-galaxy-qs.md @@ -20,11 +20,8 @@ In this quickstart guide, you'll learn how to use dbt Cloud with [Starburst Gala - Schedule a job to run. - Connect to multiple data sources in addition to your S3 bucket. -:::tip Videos for you -You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. +Check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free and [Build Better Data Pipelines with dbt and Starburst](https://www.youtube.com/watch?v=tfWm4dWgwRg) YouTube video produced by Starburst Data, Inc if you're interested in course learning with videos. -You can also watch the [Build Better Data Pipelines with dbt and Starburst](https://www.youtube.com/watch?v=tfWm4dWgwRg) YouTube video produced by Starburst Data, Inc. -::: ### Prerequisites diff --git a/website/docs/reference/dbt-jinja-functions/as_text.md b/website/docs/reference/dbt-jinja-functions/as_text.md index 6b26cfa327d..5c25147ee1b 100644 --- a/website/docs/reference/dbt-jinja-functions/as_text.md +++ b/website/docs/reference/dbt-jinja-functions/as_text.md @@ -5,19 +5,20 @@ id: "as_text" description: "Use this filter to convert Jinja-compiled output back to text." --- -The `as_text` Jinja filter will coerce Jinja-compiled output back to text. It -can be used in YAML rendering contexts where values _must_ be provided as -strings, rather than as the datatype that they look like. +:::info -:::info Heads up -In dbt v0.17.1, native rendering is not enabled by default. As such, -the `as_text` filter has no functional effect. +Native rendering is not enabled by default. As such, the `as_text` filter has no functional effect. It is still possible to natively render specific values using the [`as_bool`](/reference/dbt-jinja-functions/as_bool), [`as_number`](/reference/dbt-jinja-functions/as_number), and [`as_native`](/reference/dbt-jinja-functions/as_native) filters. ::: +The `as_text` Jinja filter will coerce Jinja-compiled output back to text. It +can be used in YAML rendering contexts where values _must_ be provided as +strings, rather than as the datatype that they look like. + + ### Usage In the example below, the `as_text` filter is used to assert that `''` is an diff --git a/website/docs/reference/dbt-jinja-functions/env_var.md b/website/docs/reference/dbt-jinja-functions/env_var.md index f4cc05cec0f..fd2a21d9cc3 100644 --- a/website/docs/reference/dbt-jinja-functions/env_var.md +++ b/website/docs/reference/dbt-jinja-functions/env_var.md @@ -100,6 +100,7 @@ select 1 as id -:::info dbt Cloud Usage +### dbt Cloud Usage + If you are using dbt Cloud, you must adhere to the naming conventions for environment variables. Environment variables in dbt Cloud must be prefixed with `DBT_` (including `DBT_ENV_CUSTOM_ENV_` or `DBT_ENV_SECRET_`). Environment variables keys are uppercased and case sensitive. When referencing `{{env_var('DBT_KEY')}}` in your project's code, the key must match exactly the variable defined in dbt Cloud's UI. -::: + diff --git a/website/docs/reference/dbt_project.yml.md b/website/docs/reference/dbt_project.yml.md index a5ad601f78b..adc415825f6 100644 --- a/website/docs/reference/dbt_project.yml.md +++ b/website/docs/reference/dbt_project.yml.md @@ -1,6 +1,8 @@ Every [dbt project](/docs/build/projects) needs a `dbt_project.yml` file — this is how dbt knows a directory is a dbt project. It also contains important information that tells dbt how to operate your project. +dbt uses YAML in a few different places. If you're new to YAML, it would be worth taking the time to learn how arrays, dictionaries, and strings are represented. + By default, dbt will look for `dbt_project.yml` in your current working directory and its parents, but you can set a different directory using the `--project-dir` flag. @@ -15,11 +17,6 @@ Starting from dbt v1.5 and higher, you can specify your dbt Cloud project ID in -:::info YAML syntax -dbt uses YAML in a few different places. If you're new to YAML, it would be worth taking the time to learn how arrays, dictionaries, and strings are represented. -::: - - Something to note, you can't set up a "property" in the `dbt_project.yml` file if it's not a config (an example is [macros](/reference/macro-properties)). This applies to all types of resources. Refer to [Configs and properties](/reference/configs-and-properties) for more detail. The following example is a list of all available configurations in the `dbt_project.yml` file: diff --git a/website/docs/reference/node-selection/methods.md b/website/docs/reference/node-selection/methods.md index 61fd380e11b..549bc5d45e1 100644 --- a/website/docs/reference/node-selection/methods.md +++ b/website/docs/reference/node-selection/methods.md @@ -8,9 +8,6 @@ you can omit it (the default value will be one of `path`, `file` or `fqn`). -:::info New functionality -New in v1.5! -::: Many of the methods below support Unix-style wildcards: diff --git a/website/docs/reference/project-configs/clean-targets.md b/website/docs/reference/project-configs/clean-targets.md index 9b464840723..0dacfc6ed90 100644 --- a/website/docs/reference/project-configs/clean-targets.md +++ b/website/docs/reference/project-configs/clean-targets.md @@ -19,10 +19,11 @@ Optionally specify a custom list of directories to be removed by the `dbt clean` If this configuration is not included in your `dbt_project.yml` file, the `clean` command will remove files in your [target-path](/reference/project-configs/target-path). ## Examples + ### Remove packages and compiled files as part of `dbt clean` -:::info + This is our preferred configuration, but is not the default. -::: + To remove packages as well as compiled files, include the value of your [packages-install-path](/reference/project-configs/packages-install-path) configuration in your `clean-targets` configuration. diff --git a/website/docs/reference/project-configs/docs-paths.md b/website/docs/reference/project-configs/docs-paths.md index 2aee7b31ee7..910cfbb0cce 100644 --- a/website/docs/reference/project-configs/docs-paths.md +++ b/website/docs/reference/project-configs/docs-paths.md @@ -20,12 +20,9 @@ Optionally specify a custom list of directories where [docs blocks](/docs/collab By default, dbt will search in all resource paths for docs blocks (i.e. the combined list of [model-paths](/reference/project-configs/model-paths), [seed-paths](/reference/project-configs/seed-paths), [analysis-paths](/reference/project-configs/analysis-paths), [macro-paths](/reference/project-configs/macro-paths) and [snapshot-paths](/reference/project-configs/snapshot-paths)). If this option is configured, dbt will _only_ look in the specified directory for docs blocks. -## Examples -:::info -We typically omit this configuration as we prefer dbt's default behavior. -::: +## Example -### Use a subdirectory named `docs` for docs blocks +Use a subdirectory named `docs` for docs blocks: @@ -34,3 +31,5 @@ docs-paths: ["docs"] ``` + +**Note:** We typically omit this configuration as we prefer dbt's default behavior. diff --git a/website/docs/reference/project-configs/require-dbt-version.md b/website/docs/reference/project-configs/require-dbt-version.md index 85a502bff60..6db54f42517 100644 --- a/website/docs/reference/project-configs/require-dbt-version.md +++ b/website/docs/reference/project-configs/require-dbt-version.md @@ -19,7 +19,7 @@ When you set this configuration, dbt sends a helpful error message for any user If this configuration is not specified, no version check will occur. -:::info YAML Quoting +### YAML Quoting This configuration needs to be interpolated by the YAML parser as a string. As such, you should quote the value of the configuration, taking care to avoid whitespace. For example: ```yml @@ -32,8 +32,6 @@ require-dbt-version: >=1.0.0 # No quotes? No good require-dbt-version: ">= 1.0.0" # Don't put whitespace after the equality signs ``` -::: - ## Examples @@ -72,19 +70,16 @@ require-dbt-version: ">=1.0.0,<2.0.0" -### Require a specific dbt version -:::caution Not recommended -With the release of major version 1.0 of dbt Core, pinning to a specific patch is discouraged. -::: +### Require a specific dbt version (not recommended) While you can restrict your project to run only with an exact version of dbt Core, we do not recommend this for dbt Core v1.0.0 and higher. -In the following example, the project will only run with dbt v0.21.1. +In the following example, the project will only run with dbt v1.5: ```yml -require-dbt-version: 0.21.1 +require-dbt-version: 1.5 ``` diff --git a/website/docs/reference/resource-configs/contract.md b/website/docs/reference/resource-configs/contract.md index ccc10099a12..6c11b08dd62 100644 --- a/website/docs/reference/resource-configs/contract.md +++ b/website/docs/reference/resource-configs/contract.md @@ -6,16 +6,7 @@ default_value: {contract: false} id: "contract" --- -:::info New functionality -This functionality is new in v1.5. -::: - -## Related documentation -- [What is a model contract?](/docs/collaborate/govern/model-contracts) -- [Defining `columns`](/reference/resource-properties/columns) -- [Defining `constraints`](/reference/resource-properties/constraints) - -# Definition +Supported in dbt v1.5 and higher. When the `contract` configuration is enforced, dbt will ensure that your model's returned dataset exactly matches the attributes you have defined in yaml: - `name` and `data_type` for every column @@ -120,3 +111,8 @@ Imagine: - The result is a delta between the yaml-defined contract, and the actual table in the database - which means the contract is now incorrect! Why `append_new_columns`, rather than `sync_all_columns`? Because removing existing columns is a breaking change for contracted models! + +## Related documentation +- [What is a model contract?](/docs/collaborate/govern/model-contracts) +- [Defining `columns`](/reference/resource-properties/columns) +- [Defining `constraints`](/reference/resource-properties/constraints) \ No newline at end of file diff --git a/website/docs/reference/resource-configs/delimiter.md b/website/docs/reference/resource-configs/delimiter.md index 58d6ba8344a..f9612d8aac6 100644 --- a/website/docs/reference/resource-configs/delimiter.md +++ b/website/docs/reference/resource-configs/delimiter.md @@ -4,19 +4,14 @@ datatype: default_value: "," --- +Supported in v1.7 and higher + ## Definition You can use this optional seed configuration to customize how you separate values in a [seed](/docs/build/seeds) by providing the one-character string. * The delimiter defaults to a comma when not specified. * Explicitly set the `delimiter` configuration value if you want seed files to use a different delimiter, such as "|" or ";". - -:::info New in 1.7! - -Delimiter is new functionality available beginning with dbt Core v1.7. - -::: - ## Usage diff --git a/website/docs/reference/resource-configs/group.md b/website/docs/reference/resource-configs/group.md index a71935013c4..e8370d18638 100644 --- a/website/docs/reference/resource-configs/group.md +++ b/website/docs/reference/resource-configs/group.md @@ -3,10 +3,6 @@ resource_types: [models, seeds, snapshots, tests, analyses, metrics] id: "group" --- -:::info New functionality -This functionality is new in v1.5. -::: - views). diff --git a/website/docs/reference/resource-properties/schema.md b/website/docs/reference/resource-properties/schema.md index 9e6a09b8569..157a9ffc0a2 100644 --- a/website/docs/reference/resource-properties/schema.md +++ b/website/docs/reference/resource-properties/schema.md @@ -27,12 +27,10 @@ The schema name as stored in the database. This parameter is useful if you want to use a source name that differs from the schema name. -:::info #### BigQuery terminology -If you're using BigQuery, use the _dataset_ name as the `schema:` property. -::: +If you're using BigQuery, use the _dataset_ name as the `schema:` property. ## Default By default, dbt will use the source's `name:` parameter as the schema name. diff --git a/website/docs/sql-reference/aggregate-functions/sql-avg.md b/website/docs/sql-reference/aggregate-functions/sql-avg.md index d1dba119292..1512cee7763 100644 --- a/website/docs/sql-reference/aggregate-functions/sql-avg.md +++ b/website/docs/sql-reference/aggregate-functions/sql-avg.md @@ -17,6 +17,8 @@ The AVG function is a part of the group of mathematical or aggregate functions ( ### AVG function example +The following example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop): + ```sql select date_trunc('month', order_date) as order_month, @@ -26,10 +28,6 @@ where status not in ('returned', 'return_pending') group by 1 ``` -:::note What dataset is this? -This example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop). -::: - This query using the Jaffle Shop’s `orders` table will return the rounded order amount per each order month: | order_month | avg_order_amount | diff --git a/website/docs/sql-reference/aggregate-functions/sql-count.md b/website/docs/sql-reference/aggregate-functions/sql-count.md index d65c670df90..1438b7c11d5 100644 --- a/website/docs/sql-reference/aggregate-functions/sql-count.md +++ b/website/docs/sql-reference/aggregate-functions/sql-count.md @@ -25,6 +25,8 @@ Let’s take a look at a practical example using COUNT, DISTINCT, and GROUP BY b ### COUNT example +The following example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop): + ```sql select date_part('month', order_date) as order_month, @@ -34,9 +36,6 @@ from {{ ref('orders') }} group by 1 ``` -:::note What dataset is this? -This example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop). -::: This simple query is something you may do while doing initial exploration of your data; it will return the count of `order_ids` and count of distinct `customer_ids` per order month that appear in the Jaffle Shop’s `orders` table: diff --git a/website/docs/sql-reference/aggregate-functions/sql-max.md b/website/docs/sql-reference/aggregate-functions/sql-max.md index 0b5dc5521ea..fab72770af5 100644 --- a/website/docs/sql-reference/aggregate-functions/sql-max.md +++ b/website/docs/sql-reference/aggregate-functions/sql-max.md @@ -25,6 +25,8 @@ Let’s take a look at a practical example using MAX and GROUP BY below. ### MAX example +The following example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop): + ```sql select date_part('month', order_date) as order_month, @@ -33,10 +35,6 @@ from {{ ref('orders') }} group by 1 ``` -:::note What dataset is this? -This example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop). -::: - This simple query is something you may do while doing initial exploration of your data; it will return the maximum order `amount` per order month that appear in the Jaffle Shop’s `orders` table: | order_month | max_amount | diff --git a/website/docs/sql-reference/aggregate-functions/sql-min.md b/website/docs/sql-reference/aggregate-functions/sql-min.md index 6080bb20c0b..95de0af8df3 100644 --- a/website/docs/sql-reference/aggregate-functions/sql-min.md +++ b/website/docs/sql-reference/aggregate-functions/sql-min.md @@ -27,6 +27,8 @@ Let’s take a look at a practical example using MIN below. ### MIN example +The following example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop): + ```sql select customer_id, @@ -37,10 +39,6 @@ group by 1 limit 3 ``` -:::note What dataset is this? -This example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop). -::: - This simple query is returning the first and last order date for a customer in the Jaffle Shop’s `orders` table: | customer_id | first_order_date | last_order_date | diff --git a/website/docs/sql-reference/aggregate-functions/sql-round.md b/website/docs/sql-reference/aggregate-functions/sql-round.md index bc9669e22cb..a080f5a63e5 100644 --- a/website/docs/sql-reference/aggregate-functions/sql-round.md +++ b/website/docs/sql-reference/aggregate-functions/sql-round.md @@ -24,11 +24,8 @@ In this function, you’ll need to input the *numeric* field or data you want ro ### SQL ROUND function example -:::note What dataset is this? -This example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop). -::: -You can round some of the numeric fields of the Jaffle Shop’s `orders` model using the following code: +You can round some of the numeric fields of the [Jaffle Shop’s](https://github.com/dbt-labs/jaffle_shop) `orders` model using the following code: ```sql select diff --git a/website/docs/sql-reference/aggregate-functions/sql-sum.md b/website/docs/sql-reference/aggregate-functions/sql-sum.md index d6ca00c2daa..494a3863ad3 100644 --- a/website/docs/sql-reference/aggregate-functions/sql-sum.md +++ b/website/docs/sql-reference/aggregate-functions/sql-sum.md @@ -27,6 +27,8 @@ Let’s take a look at a practical example using the SUM function below. ### SUM example +The following example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop): + ```sql select customer_id, @@ -36,10 +38,6 @@ group by 1 limit 3 ``` -:::note What dataset is this? -This example is querying from a sample dataset created by dbt Labs called [jaffle_shop](https://github.com/dbt-labs/jaffle_shop). -::: - This simple query is returning the summed amount of all orders for a customer in the Jaffle Shop’s `orders` table: | customer_id | all_orders_amount | diff --git a/website/docs/terms/data-extraction.md b/website/docs/terms/data-extraction.md index bc37b68cf66..52148a35421 100644 --- a/website/docs/terms/data-extraction.md +++ b/website/docs/terms/data-extraction.md @@ -37,7 +37,7 @@ Obviously, the type of business you work for and the systems your team uses will The data that is typically extracted and loaded in your data warehouse is data that business users will need for baseline reporting, OKR measurement, or other analytics. :::tip Don’t fix what’s not broken -As we just said, there are usually common data sources that data teams will extract from, regardless of business. Instead of writing transformations for these tables and data sources, leverage [dbt packages](https://hub.getdbt.com/) to save yourself some carpal tunnel and use the work someone else has already done for you :) +As we just said, there are usually common data sources that data teams will extract from, regardless of business. Instead of writing transformations for these tables and data sources, leverage [dbt packages](https://hub.getdbt.com/) to save yourself some carpal tunnel and use the work someone else has already done for you. ::: ## Data extraction tools diff --git a/website/docs/terms/table.md b/website/docs/terms/table.md index cbe36ec1315..bfc4e680660 100644 --- a/website/docs/terms/table.md +++ b/website/docs/terms/table.md @@ -5,9 +5,6 @@ description: "Read this guide to understand how tables work in dbt." displayText: table hoverSnippet: In simplest terms, a table is the direct storage of data in rows and columns. Think excel sheet with raw values in each of the cells. --- -:::important This page could use some love -This term would benefit from additional depth and examples. Have knowledge to contribute? [Create an issue in the docs.getdbt.com repository](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose) to begin the process of becoming a glossary contributor! -::: In simplest terms, a table is the direct storage of data in rows and columns. Think excel sheet with raw values in each of the cells. diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index 6b6eb1c2761..c7e67fdb547 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -28,13 +28,12 @@ Both development and deployment environments have a section called **General Set | Default to Custom Branch | ☑️ | Determines whether to use a branch other than the repository’s default | See below | | Custom Branch | dev | Custom Branch name | See below | -:::note About dbt version +### About versions in dbt Cloud -- dbt Cloud allows users to select any dbt release. At this time, **environments must use a dbt version greater than or equal to v1.0.0;** [lower versions are no longer supported](/docs/dbt-versions/upgrade-core-in-cloud). -- If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. -::: +dbt Cloud allows users to select from multiple dbt releases. At this time, environments must use a dbt version greater than or equal to v1.0.0 [lower versions are no longer supported](/docs/dbt-versions/upgrade-core-in-cloud). +If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. -### Git repository caching +### Git repository caching (Enterprise plans only) At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. @@ -53,11 +52,6 @@ To enable Git repository caching, select **Account settings** from the gear menu -:::note - -This feature is only available on the dbt Cloud Enterprise plan. - -::: ### Custom branch behavior diff --git a/website/snippets/_upgrade-move.md b/website/snippets/_upgrade-move.md deleted file mode 100644 index 7572077fd1b..00000000000 --- a/website/snippets/_upgrade-move.md +++ /dev/null @@ -1,5 +0,0 @@ -:::important Upgrade Guides Are Moving - -The location of the dbt Core upgrade guides has changed, and they will soon be removed from `Guides`. The new location is in the `Docs` tab under `Available dbt versions`. You have been redirected to the new URL, so please update any saved links and bookmarks. - -::: \ No newline at end of file diff --git a/website/snippets/available-prerelease-banner.md b/website/snippets/available-prerelease-banner.md deleted file mode 100644 index 3531a2f646f..00000000000 --- a/website/snippets/available-prerelease-banner.md +++ /dev/null @@ -1,7 +0,0 @@ -:::info Release candidate -dbt Core v1.2 is now available as a **release candidate**. - -For more information on prereleases, see ["About Core versions: Trying prereleases"](core-versions#trying-prereleases). - -Join the [#dbt-prereleases](https://getdbt.slack.com/archives/C016X6ABVUK) channel in the Community Slack so you can be the first to read about prereleases as soon as they're available! -::: diff --git a/website/snippets/quickstarts/schedule-a-job.md b/website/snippets/quickstarts/schedule-a-job.md index ab8f4350dbf..70848388f35 100644 --- a/website/snippets/quickstarts/schedule-a-job.md +++ b/website/snippets/quickstarts/schedule-a-job.md @@ -35,9 +35,9 @@ As the `jaffle_shop` business gains more customers, and those customers create m 8. Click the run and watch its progress under "Run history." 9. Once the run is complete, click **View Documentation** to see the docs for your project. -:::tip + Congratulations 🎉! You've just deployed your first dbt project! -::: + #### FAQs From e73a361d51c3fb8a8cc80667704d29557c1f7aee Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 09:23:00 -0500 Subject: [PATCH 02/25] Update website/snippets/_cloud-environments-info.md --- website/snippets/_cloud-environments-info.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index 9a1941e6e4f..394339612d4 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -34,7 +34,7 @@ dbt Cloud allows users to select from multiple dbt releases. At this time, envir If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. -### Git repository caching (Enterprise plans only) +### Git repository caching At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. From 070e549984b36c161a225a20195292e39c3cb2c0 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 09:27:08 -0500 Subject: [PATCH 03/25] Update website/snippets/_cloud-environments-info.md Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- website/snippets/_cloud-environments-info.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index 394339612d4..0e00596b97a 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -30,7 +30,9 @@ Both development and deployment environments have a section called **General Set ### About versions in dbt Cloud -dbt Cloud allows users to select from multiple dbt releases. At this time, environments must use a dbt version greater than or equal to v1.0.0 [lower versions are no longer supported](/docs/dbt-versions/upgrade-core-in-cloud). +- Multiple dbt releases: dbt Cloud enables users to choose from various dbt versions. +- Version requirements: Environments must use dbt version v1.0.0 or higher. [Lower versions are not supported](/docs/dbt-versions/upgrade-core-in-cloud). +- Automatic updates: Selecting a version labeled `(latest)` ensures your environment automatically installs the latest stable release of that minor version selected. If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. From 83ac67b0e4acaabff369e362cb5c559eba33fa20 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 09:28:10 -0500 Subject: [PATCH 04/25] Update website/snippets/_cloud-environments-info.md Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- website/snippets/_cloud-environments-info.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index 0e00596b97a..6ad3a136d54 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -33,7 +33,6 @@ Both development and deployment environments have a section called **General Set - Multiple dbt releases: dbt Cloud enables users to choose from various dbt versions. - Version requirements: Environments must use dbt version v1.0.0 or higher. [Lower versions are not supported](/docs/dbt-versions/upgrade-core-in-cloud). - Automatic updates: Selecting a version labeled `(latest)` ensures your environment automatically installs the latest stable release of that minor version selected. -If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. ### Git repository caching From 121c3c77a260bd26518a12d7b5db4090c6192b66 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 10:57:28 -0500 Subject: [PATCH 05/25] Update website/docs/reference/project-configs/require-dbt-version.md Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- .../docs/reference/project-configs/require-dbt-version.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/docs/reference/project-configs/require-dbt-version.md b/website/docs/reference/project-configs/require-dbt-version.md index 6db54f42517..7aaf9859e86 100644 --- a/website/docs/reference/project-configs/require-dbt-version.md +++ b/website/docs/reference/project-configs/require-dbt-version.md @@ -70,7 +70,10 @@ require-dbt-version: ">=1.0.0,<2.0.0" -### Require a specific dbt version (not recommended) +### Require a specific dbt version + +:::info Not recommended +Pinning to a specific dbt version is discouraged because it limits project flexibility and can cause compatibility issues, especially with dbt packages. It's recommended to [pin to a major release](#pin-to-a-range), using a version range (for example, `">=1.0.0", "<2.0.0"`) for broader compatibility and to benefit from updates. While you can restrict your project to run only with an exact version of dbt Core, we do not recommend this for dbt Core v1.0.0 and higher. From c042f0717b67631d4392a716b4f3a728a4e63118 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 10:57:52 -0500 Subject: [PATCH 06/25] Update website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md Co-authored-by: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> --- .../how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md b/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md index ae10cd8f521..7898a992ea8 100644 --- a/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md +++ b/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md @@ -131,7 +131,7 @@ if __name__ == '__main__': * To find these values, navigate to **dbt Cloud**, select **Deploy -> Jobs**. Select the Job you want to run and copy the URL. For example: `https://cloud.getdbt.com/deploy/000000/projects/111111/jobs/222222` and therefore valid code would be: - Your URL is structured https:///deploy//projects//jobs/ +Your URL is structured `https:///deploy//projects//jobs/` account_id = 000000 job_id = 222222 base_url = "cloud.getdbt.com" From ade0bfba8f414970e3d9922a5156fc76571b12b6 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 10:59:07 -0500 Subject: [PATCH 07/25] Update website/docs/reference/dbt_project.yml.md --- website/docs/reference/dbt_project.yml.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/dbt_project.yml.md b/website/docs/reference/dbt_project.yml.md index adc415825f6..ae911200b40 100644 --- a/website/docs/reference/dbt_project.yml.md +++ b/website/docs/reference/dbt_project.yml.md @@ -1,7 +1,7 @@ Every [dbt project](/docs/build/projects) needs a `dbt_project.yml` file — this is how dbt knows a directory is a dbt project. It also contains important information that tells dbt how to operate your project. -dbt uses YAML in a few different places. If you're new to YAML, it would be worth taking the time to learn how arrays, dictionaries, and strings are represented. +dbt uses [YAML](https://yaml.org/) in a few different places. If you're new to YAML, it would be worth learning how arrays, dictionaries, and strings are represented. From 309ab75db47e8a3cecd88335d02c1cadf5b07444 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 11:56:04 -0500 Subject: [PATCH 08/25] Update website/snippets/_cloud-environments-info.md --- website/snippets/_cloud-environments-info.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index 6ad3a136d54..f9391c23647 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -35,7 +35,7 @@ Both development and deployment environments have a section called **General Set - Automatic updates: Selecting a version labeled `(latest)` ensures your environment automatically installs the latest stable release of that minor version selected. -### Git repository caching +### Git repository caching At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. From 693f9d791497779e01dc945976884294c55dc585 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 11:57:25 -0500 Subject: [PATCH 09/25] Update website/snippets/_cloud-environments-info.md --- website/snippets/_cloud-environments-info.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md index f9391c23647..c4675d4d7a8 100644 --- a/website/snippets/_cloud-environments-info.md +++ b/website/snippets/_cloud-environments-info.md @@ -36,7 +36,9 @@ Both development and deployment environments have a section called **General Set ### Git repository caching - +:::info Available for dbt Cloud Enterprise plans +This feature is exclusively available for dbt Cloud Enterprise plans. [Book a demo](https://www.getdbt.com/contact) to learn more. +::: At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. For improved reliability and performance on your job runs, you can enable dbt Cloud to keep a cache of the project's Git repository. So, if there's a third-party outage that causes the cloning operation to fail, dbt Cloud will instead use the cached copy of the repo so your jobs can continue running as scheduled. From 0099b29741acfb8c6fe4826ca299cb43200a9092 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 12:06:33 -0500 Subject: [PATCH 10/25] Update website/docs/reference/project-configs/clean-targets.md --- website/docs/reference/project-configs/clean-targets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/project-configs/clean-targets.md b/website/docs/reference/project-configs/clean-targets.md index 0dacfc6ed90..e3c05cb0abd 100644 --- a/website/docs/reference/project-configs/clean-targets.md +++ b/website/docs/reference/project-configs/clean-targets.md @@ -20,7 +20,7 @@ If this configuration is not included in your `dbt_project.yml` file, the `clean ## Examples -### Remove packages and compiled files as part of `dbt clean` +### Remove packages and compiled files as part of `dbt clean` (preferred) This is our preferred configuration, but is not the default. From 1808b95f6454d875e79dd6474cd63d2466923ce1 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Tue, 9 Jan 2024 12:07:18 -0500 Subject: [PATCH 11/25] Update website/docs/reference/project-configs/clean-targets.md --- website/docs/reference/project-configs/clean-targets.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/reference/project-configs/clean-targets.md b/website/docs/reference/project-configs/clean-targets.md index e3c05cb0abd..d248166ff56 100644 --- a/website/docs/reference/project-configs/clean-targets.md +++ b/website/docs/reference/project-configs/clean-targets.md @@ -22,7 +22,6 @@ If this configuration is not included in your `dbt_project.yml` file, the `clean ### Remove packages and compiled files as part of `dbt clean` (preferred) -This is our preferred configuration, but is not the default. To remove packages as well as compiled files, include the value of your [packages-install-path](/reference/project-configs/packages-install-path) configuration in your `clean-targets` configuration. From d7170e8e5041ef85e688a7d2b3038aa7a87bad79 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 11:37:06 -0500 Subject: [PATCH 12/25] Update website/docs/faqs/Accounts/cloud-upgrade-instructions.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- website/docs/faqs/Accounts/cloud-upgrade-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/faqs/Accounts/cloud-upgrade-instructions.md b/website/docs/faqs/Accounts/cloud-upgrade-instructions.md index c3ccade3e4a..d16651a944c 100644 --- a/website/docs/faqs/Accounts/cloud-upgrade-instructions.md +++ b/website/docs/faqs/Accounts/cloud-upgrade-instructions.md @@ -9,7 +9,7 @@ dbt Cloud offers [several plans](https://www.getdbt.com/pricing/) with different ## Prerequisites Before you begin: -- You **_must_** be part of the [Owner](/docs/cloud/manage-access/self-service-permissions) user group to make billing changes. Users not included in this group will not see these options. +- You _must_ be part of the [Owner](/docs/cloud/manage-access/self-service-permissions) user group to make billing changes. Users not included in this group will not see these options. - All amounts shown in dbt Cloud are in U.S. Dollars (USD) - When your trial expires, your account's default plan enrollment will be a Team plan. From 60e619924f7e1ad97aae25b27750599345837a24 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 11:38:40 -0500 Subject: [PATCH 13/25] Update website/docs/guides/debug-schema-names.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- website/docs/guides/debug-schema-names.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/debug-schema-names.md b/website/docs/guides/debug-schema-names.md index 94e1df673b8..24b7984adf5 100644 --- a/website/docs/guides/debug-schema-names.md +++ b/website/docs/guides/debug-schema-names.md @@ -91,7 +91,7 @@ Now, re-read through the logic of your `generate_schema_name` macro, and mentall You should find that the schema dbt is constructing for your model matches the output of your `generate_schema_name` macro. -**Note:** Snapshots do not follow this behavior, check out the docs on [target_schema](/reference/resource-configs/target_schema) instead. +Be careful. Snapshots do not follow this behavior, check out the docs on [target_schema](/reference/resource-configs/target_schema) instead. ## Adjust as necessary From cf324f64bf7b3d4f770bead383c4167cde2fdc74 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 11:48:43 -0500 Subject: [PATCH 14/25] Delete website/snippets/_cloud-environments-info.md --- website/snippets/_cloud-environments-info.md | 137 ------------------- 1 file changed, 137 deletions(-) delete mode 100644 website/snippets/_cloud-environments-info.md diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md deleted file mode 100644 index c4675d4d7a8..00000000000 --- a/website/snippets/_cloud-environments-info.md +++ /dev/null @@ -1,137 +0,0 @@ - -## Types of environments - -In dbt Cloud, there are two types of environments: -- Deployment environment — Determines the settings used when jobs created within that environment are executed. -- Development environment — Determines the settings used in the dbt Cloud IDE or dbt Cloud CLI, for that particular project. - -Each dbt Cloud project can only have a single development environment but can have any number of deployment environments. - -| | Development Environments | Deployment Environments | -| --- | --- | --- | -| Determines settings for | dbt Cloud IDE or dbt Cloud CLI | dbt Cloud Job runs | -| How many can I have in my project? | 1 | Any number | - -:::note -For users familiar with development on dbt Core, each environment is roughly analogous to an entry in your `profiles.yml` file, with some additional information about your repository to ensure the proper version of code is executed. More info on dbt core environments [here](/docs/core/dbt-core-environments). -::: - -## Common environment settings - -Both development and deployment environments have a section called **General Settings**, which has some basic settings that all environments will define: - -| Setting | Example Value | Definition | Accepted Values | -| --- | --- | --- | --- | -| Name | Production | The environment name | Any string! | -| Environment Type | Deployment | The type of environment | [Deployment, Development] | -| dbt Version | 1.4 (latest) | The dbt version used | Any dbt version in the dropdown | -| Default to Custom Branch | ☑️ | Determines whether to use a branch other than the repository’s default | See below | -| Custom Branch | dev | Custom Branch name | See below | - -### About versions in dbt Cloud - -- Multiple dbt releases: dbt Cloud enables users to choose from various dbt versions. -- Version requirements: Environments must use dbt version v1.0.0 or higher. [Lower versions are not supported](/docs/dbt-versions/upgrade-core-in-cloud). -- Automatic updates: Selecting a version labeled `(latest)` ensures your environment automatically installs the latest stable release of that minor version selected. - - -### Git repository caching -:::info Available for dbt Cloud Enterprise plans -This feature is exclusively available for dbt Cloud Enterprise plans. [Book a demo](https://www.getdbt.com/contact) to learn more. -::: -At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. - -For improved reliability and performance on your job runs, you can enable dbt Cloud to keep a cache of the project's Git repository. So, if there's a third-party outage that causes the cloning operation to fail, dbt Cloud will instead use the cached copy of the repo so your jobs can continue running as scheduled. - -dbt Cloud caches your project's Git repo after each successful run and retains it for 8 days if there are no repo updates. It caches all packages regardless of installation method and does not fetch code outside of the job runs. - -dbt Cloud will use the cached copy of your project's Git repo under these circumstances: - -- Outages from third-party services (for example, the [dbt package hub](https://hub.getdbt.com/)). -- Git authentication fails. -- There are syntax errors in the `packages.yml` file. You can set up and use [continuous integration (CI)](/docs/deploy/continuous-integration) to find these errors sooner. -- If a package doesn't work with the current dbt version. You can set up and use [continuous integration (CI)](/docs/deploy/continuous-integration) to identify this issue sooner. - -To enable Git repository caching, select **Account settings** from the gear menu and enable the **Repository caching** option. - - - -### Custom branch behavior - -By default, all environments will use the default branch in your repository (usually the `main` branch) when accessing your dbt code. This is overridable within each dbt Cloud Environment using the **Default to a custom branch** option. This setting have will have slightly different behavior depending on the environment type: - -- **Development**: determines which branch in the dbt Cloud IDE or dbt Cloud CLI developers create branches from and open PRs against. -- **Deployment:** determines the branch is cloned during job executions for each environment. - -For more info, check out this [FAQ page on this topic](/faqs/Environments/custom-branch-settings)! - - -### Extended attributes - -:::note -Extended attributes are retrieved and applied only at runtime when `profiles.yml` is requested for a specific Cloud run. Extended attributes are currently _not_ taken into consideration for Cloud-specific features such as PrivateLink or SSH Tunneling that do not rely on `profiles.yml` values. -::: - -Extended Attributes is a feature that allows users to set a flexible [profiles.yml](/docs/core/connect-data-platform/profiles.yml) snippet in their dbt Cloud Environment settings. It provides users with more control over environments (both deployment and development) and extends how dbt Cloud connects to the data platform within a given environment. - -Extended Attributes is a text box extension at the environment level that overrides connection or environment credentials, including any custom environment variables. You can set any YAML attributes that a dbt adapter accepts in its `profiles.yml`. - -Something to note, Extended Attributes doesn't mask secret values. We recommend avoiding setting secret values to prevent visibility in the text box and logs. - -
- -If you're developing in the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud), [dbt Cloud CLI](/docs/cloud/cloud-cli-installation), or [orchestrating job runs](/docs/deploy/deployments), Extended Attributes parses through the provided YAML and extracts the `profiles.yml` attributes. For each individual attribute: - -- If the attribute exists in another source (such as your project settings), it will replace its value (like environment-level values) in the profile. It also overrides any custom environment variables. - -- If the attribute doesn't exist, it will add the attribute or value pair to the profile. - -Only the **top-level keys** are accepted in extended attributes. This means that if you want to change a specific sub-key value, you must provide the entire top-level key as a JSON block in your resulting YAML. For example, if you want to customize a particular field within a [service account JSON](/docs/core/connect-data-platform/bigquery-setup#service-account-json) for your BigQuery connection (like 'project_id' or 'client_email'), you need to provide an override for the entire top-level `keyfile_json` main key/attribute using extended attributes. Include the sub-fields as a nested JSON block. - -The following code is an example of the types of attributes you can add in the **Extended Attributes** text box: - -```yaml -dbname: jaffle_shop -schema: dbt_alice -threads: 4 -``` - -### Git repository caching - -At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. - -For improved reliability and performance on your job runs, you can enable dbt Cloud to keep a cache of the project's Git repository. So, if there's a third-party outage that causes the cloning operation to fail, dbt Cloud will instead use the cached copy of the repo so your jobs can continue running as scheduled. - -dbt Cloud caches your project's Git repo after each successful run and retains it for 8 days if there are no repo updates. It caches all packages regardless of installation method and does not fetch code outside of the job runs. - -dbt Cloud will use the cached copy of your project's Git repo under these circumstances: - -- Outages from third-party services (for example, the [dbt package hub](https://hub.getdbt.com/)). -- Git authentication fails. -- There are syntax errors in the `packages.yml` file. You can set up and use [continuous integration (CI)](/docs/deploy/continuous-integration) to find these errors sooner. -- If a package doesn't work with the current dbt version. You can set up and use [continuous integration (CI)](/docs/deploy/continuous-integration) to identify this issue sooner. - -To enable Git repository caching, select **Account settings** from the gear menu and enable the **Repository caching** option. - - - -:::note - -This feature is only available on the dbt Cloud Enterprise plan. - -::: - -### Partial parsing - -At the start of every dbt invocation, dbt reads all the files in your project, extracts information, and constructs an internal manifest containing every object (model, source, macro, and so on). Among other things, it uses the `ref()`, `source()`, and `config()` macro calls within models to set properties, infer dependencies, and construct your project's DAG. When dbt finishes parsing your project, it stores the internal manifest in a file called `partial_parse.msgpack`. - -Parsing projects can be time-consuming, especially for large projects with hundreds of models and thousands of files. To reduce the time it takes dbt to parse your project, use the partial parsing feature in dbt Cloud for your environment. When enabled, dbt Cloud uses the `partial_parse.msgpack` file to determine which files have changed (if any) since the project was last parsed, and then it parses _only_ the changed files and the files related to those changes. - -Partial parsing in dbt Cloud requires dbt version 1.4 or newer. The feature does have some known limitations. Refer to [Known limitations](/reference/parsing#known-limitations) to learn more about them. - -To enable, select **Account settings** from the gear menu and enable the **Partial parsing** option. - - - - - From 383af84074238d6831d12b95da079b3beb20b2c6 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 11:58:31 -0500 Subject: [PATCH 15/25] Reverting snippet to original format --- website/snippets/_cloud-environments-info.md | 111 +++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 website/snippets/_cloud-environments-info.md diff --git a/website/snippets/_cloud-environments-info.md b/website/snippets/_cloud-environments-info.md new file mode 100644 index 00000000000..56030e5fce7 --- /dev/null +++ b/website/snippets/_cloud-environments-info.md @@ -0,0 +1,111 @@ +## Types of environments + +In dbt Cloud, there are two types of environments: +- Deployment environment — Determines the settings used when jobs created within that environment are executed. +- Development environment — Determines the settings used in the dbt Cloud IDE or dbt Cloud CLI, for that particular project. + +Each dbt Cloud project can only have a single development environment but can have any number of deployment environments. + +| | Development Environments | Deployment Environments | +| --- | --- | --- | +| Determines settings for | dbt Cloud IDE or dbt Cloud CLI | dbt Cloud Job runs | +| How many can I have in my project? | 1 | Any number | + +:::note +For users familiar with development on dbt Core, each environment is roughly analogous to an entry in your `profiles.yml` file, with some additional information about your repository to ensure the proper version of code is executed. More info on dbt core environments [here](/docs/core/dbt-core-environments). +::: + +## Common environment settings + +Both development and deployment environments have a section called **General Settings**, which has some basic settings that all environments will define: + +| Setting | Example Value | Definition | Accepted Values | +| --- | --- | --- | --- | +| Name | Production | The environment name | Any string! | +| Environment Type | Deployment | The type of environment | [Deployment, Development] | +| dbt Version | 1.4 (latest) | The dbt version used | Any dbt version in the dropdown | +| Default to Custom Branch | ☑️ | Determines whether to use a branch other than the repository’s default | See below | +| Custom Branch | dev | Custom Branch name | See below | + +:::note About dbt version + +- dbt Cloud allows users to select any dbt release. At this time, **environments must use a dbt version greater than or equal to v1.0.0;** [lower versions are no longer supported](/docs/dbt-versions/upgrade-core-in-cloud). +- If you select a current version with `(latest)` in the name, your environment will automatically install the latest stable version of the minor version selected. +::: + +### Custom branch behavior + +By default, all environments will use the default branch in your repository (usually the `main` branch) when accessing your dbt code. This is overridable within each dbt Cloud Environment using the **Default to a custom branch** option. This setting have will have slightly different behavior depending on the environment type: + +- **Development**: determines which branch in the dbt Cloud IDE or dbt Cloud CLI developers create branches from and open PRs against. +- **Deployment:** determines the branch is cloned during job executions for each environment. + +For more info, check out this [FAQ page on this topic](/faqs/Environments/custom-branch-settings)! + + +### Extended attributes + +:::note +Extended attributes are retrieved and applied only at runtime when `profiles.yml` is requested for a specific Cloud run. Extended attributes are currently _not_ taken into consideration for Cloud-specific features such as PrivateLink or SSH Tunneling that do not rely on `profiles.yml` values. +::: + +Extended Attributes is a feature that allows users to set a flexible [profiles.yml](/docs/core/connect-data-platform/profiles.yml) snippet in their dbt Cloud Environment settings. It provides users with more control over environments (both deployment and development) and extends how dbt Cloud connects to the data platform within a given environment. + +Extended Attributes is a text box extension at the environment level that overrides connection or environment credentials, including any custom environment variables. You can set any YAML attributes that a dbt adapter accepts in its `profiles.yml`. + +Something to note, Extended Attributes doesn't mask secret values. We recommend avoiding setting secret values to prevent visibility in the text box and logs. + +
+ +If you're developing in the [dbt Cloud IDE](/docs/cloud/dbt-cloud-ide/develop-in-the-cloud), [dbt Cloud CLI](/docs/cloud/cloud-cli-installation), or [orchestrating job runs](/docs/deploy/deployments), Extended Attributes parses through the provided YAML and extracts the `profiles.yml` attributes. For each individual attribute: + +- If the attribute exists in another source (such as your project settings), it will replace its value (like environment-level values) in the profile. It also overrides any custom environment variables. + +- If the attribute doesn't exist, it will add the attribute or value pair to the profile. + +Only the **top-level keys** are accepted in extended attributes. This means that if you want to change a specific sub-key value, you must provide the entire top-level key as a JSON block in your resulting YAML. For example, if you want to customize a particular field within a [service account JSON](/docs/core/connect-data-platform/bigquery-setup#service-account-json) for your BigQuery connection (like 'project_id' or 'client_email'), you need to provide an override for the entire top-level `keyfile_json` main key/attribute using extended attributes. Include the sub-fields as a nested JSON block. + +The following code is an example of the types of attributes you can add in the **Extended Attributes** text box: + +```yaml +dbname: jaffle_shop +schema: dbt_alice +threads: 4 +``` + +### Git repository caching + +At the start of every job run, dbt Cloud clones the project's Git repository so it has the latest versions of your project's code and runs `dbt deps` to install your dependencies. + +For improved reliability and performance on your job runs, you can enable dbt Cloud to keep a cache of the project's Git repository. So, if there's a third-party outage that causes the cloning operation to fail, dbt Cloud will instead use the cached copy of the repo so your jobs can continue running as scheduled. + +dbt Cloud caches your project's Git repo after each successful run and retains it for 8 days if there are no repo updates. It caches all packages regardless of installation method and does not fetch code outside of the job runs. + +dbt Cloud will use the cached copy of your project's Git repo under these circumstances: + +- Outages from third-party services (for example, the [dbt package hub](https://hub.getdbt.com/)). +- Git authentication fails. +- There are syntax errors in the `packages.yml` file. You can set up and use [continuous integration (CI)](/docs/deploy/continuous-integration) to find these errors sooner. +- If a package doesn't work with the current dbt version. You can set up and use [continuous integration (CI)](/docs/deploy/continuous-integration) to identify this issue sooner. + +To enable Git repository caching, select **Account settings** from the gear menu and enable the **Repository caching** option. + + + +:::note + +This feature is only available on the dbt Cloud Enterprise plan. + +::: + +### Partial parsing + +At the start of every dbt invocation, dbt reads all the files in your project, extracts information, and constructs an internal manifest containing every object (model, source, macro, and so on). Among other things, it uses the `ref()`, `source()`, and `config()` macro calls within models to set properties, infer dependencies, and construct your project's DAG. When dbt finishes parsing your project, it stores the internal manifest in a file called `partial_parse.msgpack`. + +Parsing projects can be time-consuming, especially for large projects with hundreds of models and thousands of files. To reduce the time it takes dbt to parse your project, use the partial parsing feature in dbt Cloud for your environment. When enabled, dbt Cloud uses the `partial_parse.msgpack` file to determine which files have changed (if any) since the project was last parsed, and then it parses _only_ the changed files and the files related to those changes. + +Partial parsing in dbt Cloud requires dbt version 1.4 or newer. The feature does have some known limitations. Refer to [Known limitations](/reference/parsing#known-limitations) to learn more about them. + +To enable, select **Account settings** from the gear menu and enable the **Partial parsing** option. + + \ No newline at end of file From 3cd46c8b2482cbce9a754733f32291c31ef6da0c Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:01:07 -0500 Subject: [PATCH 16/25] Update website/docs/reference/resource-configs/delimiter.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- website/docs/reference/resource-configs/delimiter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/delimiter.md b/website/docs/reference/resource-configs/delimiter.md index f9612d8aac6..5cc5ddaf44b 100644 --- a/website/docs/reference/resource-configs/delimiter.md +++ b/website/docs/reference/resource-configs/delimiter.md @@ -4,7 +4,7 @@ datatype: default_value: "," --- -Supported in v1.7 and higher +Supported in v1.7 and higher. ## Definition From f62d77960c73f8c71c0dd2538884f452054f52ec Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:06:08 -0500 Subject: [PATCH 17/25] Update bigquery-qs.md --- website/docs/guides/bigquery-qs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/docs/guides/bigquery-qs.md b/website/docs/guides/bigquery-qs.md index 8ef97df00e9..4f461a3cf3a 100644 --- a/website/docs/guides/bigquery-qs.md +++ b/website/docs/guides/bigquery-qs.md @@ -21,8 +21,9 @@ In this quickstart guide, you'll learn how to use dbt Cloud with BigQuery. It wi - Document your models. - Schedule a job to run. - +:::tip Videos for you You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. +::: ### Prerequisites​ From b5b4823e59619d5b689bc323d69038c54e679c4f Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:06:35 -0500 Subject: [PATCH 18/25] Update databricks-qs.md --- website/docs/guides/databricks-qs.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/docs/guides/databricks-qs.md b/website/docs/guides/databricks-qs.md index a2e08e004ed..cb01daec394 100644 --- a/website/docs/guides/databricks-qs.md +++ b/website/docs/guides/databricks-qs.md @@ -19,8 +19,9 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Databricks. It - Document your models. - Schedule a job to run. - +:::tip Videos for you You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. +::: ### Prerequisites​ From 8b5fb54735218552ec1bcfa2b95bc10ef79d7cf2 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:06:49 -0500 Subject: [PATCH 19/25] Update website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- .../how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md b/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md index 7898a992ea8..a2967ccbe15 100644 --- a/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md +++ b/website/docs/guides/how-to-use-databricks-workflows-to-run-dbt-cloud-jobs.md @@ -160,7 +160,7 @@ DbtJobRunStatus.RUNNING DbtJobRunStatus.SUCCESS ``` -**Note:** You can cancel the job from dbt Cloud if necessary. +You can cancel the job from dbt Cloud if necessary. ## Configure the workflows to run the dbt Cloud jobs From b8c4135e5e42d3c66f7205677330f67406a21d66 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:07:25 -0500 Subject: [PATCH 20/25] Update redshift-qs.md --- website/docs/guides/redshift-qs.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/guides/redshift-qs.md b/website/docs/guides/redshift-qs.md index b24d04fc0b3..c81a4d247a5 100644 --- a/website/docs/guides/redshift-qs.md +++ b/website/docs/guides/redshift-qs.md @@ -18,7 +18,9 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Redshift. It wi - Document your models - Schedule a job to run +:::tips Videos for you You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. +::: ### Prerequisites From e7a7ba5189f25a9a56887a8ec7f28cbccce16748 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:07:37 -0500 Subject: [PATCH 21/25] Update website/docs/reference/project-configs/require-dbt-version.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- website/docs/reference/project-configs/require-dbt-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/project-configs/require-dbt-version.md b/website/docs/reference/project-configs/require-dbt-version.md index 7aaf9859e86..6b17bb46120 100644 --- a/website/docs/reference/project-configs/require-dbt-version.md +++ b/website/docs/reference/project-configs/require-dbt-version.md @@ -19,7 +19,7 @@ When you set this configuration, dbt sends a helpful error message for any user If this configuration is not specified, no version check will occur. -### YAML Quoting +### YAML quoting This configuration needs to be interpolated by the YAML parser as a string. As such, you should quote the value of the configuration, taking care to avoid whitespace. For example: ```yml From 89a606f892bcf5f409fb4e477f5ac601371077ea Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:09:12 -0500 Subject: [PATCH 22/25] Update snowflake-qs.md --- website/docs/guides/snowflake-qs.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/website/docs/guides/snowflake-qs.md b/website/docs/guides/snowflake-qs.md index 2b6a00bcd68..0401c37871f 100644 --- a/website/docs/guides/snowflake-qs.md +++ b/website/docs/guides/snowflake-qs.md @@ -21,10 +21,12 @@ In this quickstart guide, you'll learn how to use dbt Cloud with Snowflake. It w Snowflake also provides a quickstart for you to learn how to use dbt Cloud. It makes use of a different public dataset (Knoema Economy Data Atlas) than what's shown in this guide. For more information, refer to [Accelerating Data Teams with dbt Cloud & Snowflake](https://quickstarts.snowflake.com/guide/accelerating_data_teams_with_snowflake_and_dbt_cloud_hands_on_lab/) in the Snowflake docs. +:::tip Videos for you +You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. -Check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free and the [YouTube video on dbt and Snowflake](https://www.youtube.com/watch?v=kbCkwhySV_I&list=PL0QYlrC86xQm7CoOH6RS7hcgLnd3OQioG) if you're interested in course learning with videos. +You can also watch the [YouTube video on dbt and Snowflake](https://www.youtube.com/watch?v=kbCkwhySV_I&list=PL0QYlrC86xQm7CoOH6RS7hcgLnd3OQioG). +::: - ### Prerequisites​ - You have a [dbt Cloud account](https://www.getdbt.com/signup/). From 672ced0b0cd9961955bc50446e1885fb9ebf4f10 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:10:38 -0500 Subject: [PATCH 23/25] Update starburst-galaxy-qs.md --- website/docs/guides/starburst-galaxy-qs.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/docs/guides/starburst-galaxy-qs.md b/website/docs/guides/starburst-galaxy-qs.md index e5c71810d0f..1822c83fa90 100644 --- a/website/docs/guides/starburst-galaxy-qs.md +++ b/website/docs/guides/starburst-galaxy-qs.md @@ -20,8 +20,11 @@ In this quickstart guide, you'll learn how to use dbt Cloud with [Starburst Gala - Schedule a job to run. - Connect to multiple data sources in addition to your S3 bucket. -Check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free and [Build Better Data Pipelines with dbt and Starburst](https://www.youtube.com/watch?v=tfWm4dWgwRg) YouTube video produced by Starburst Data, Inc if you're interested in course learning with videos. +:::tip Videos for you +You can check out [dbt Fundamentals](https://courses.getdbt.com/courses/fundamentals) for free if you're interested in course learning with videos. +You can also watch the [Build Better Data Pipelines with dbt and Starburst](https://www.youtube.com/watch?v=tfWm4dWgwRg) YouTube video produced by Starburst Data, Inc. +::: ### Prerequisites From 0005821c54bac23771676c9eb8d015b71f625af2 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:11:14 -0500 Subject: [PATCH 24/25] Update website/docs/reference/dbt-jinja-functions/env_var.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- website/docs/reference/dbt-jinja-functions/env_var.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/dbt-jinja-functions/env_var.md b/website/docs/reference/dbt-jinja-functions/env_var.md index fd2a21d9cc3..a8f2a94fbd2 100644 --- a/website/docs/reference/dbt-jinja-functions/env_var.md +++ b/website/docs/reference/dbt-jinja-functions/env_var.md @@ -100,7 +100,7 @@ select 1 as id -### dbt Cloud Usage +### dbt Cloud usage If you are using dbt Cloud, you must adhere to the naming conventions for environment variables. Environment variables in dbt Cloud must be prefixed with `DBT_` (including `DBT_ENV_CUSTOM_ENV_` or `DBT_ENV_SECRET_`). Environment variables keys are uppercased and case sensitive. When referencing `{{env_var('DBT_KEY')}}` in your project's code, the key must match exactly the variable defined in dbt Cloud's UI. From 8e2c8d031bb36f646e5a34796b15e8798e3ab5b7 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Wed, 10 Jan 2024 12:11:42 -0500 Subject: [PATCH 25/25] Update website/docs/reference/project-configs/clean-targets.md Co-authored-by: Ly Nguyen <107218380+nghi-ly@users.noreply.github.com> --- website/docs/reference/project-configs/clean-targets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/project-configs/clean-targets.md b/website/docs/reference/project-configs/clean-targets.md index d248166ff56..8ca4065ed75 100644 --- a/website/docs/reference/project-configs/clean-targets.md +++ b/website/docs/reference/project-configs/clean-targets.md @@ -20,7 +20,7 @@ If this configuration is not included in your `dbt_project.yml` file, the `clean ## Examples -### Remove packages and compiled files as part of `dbt clean` (preferred) +### Remove packages and compiled files as part of `dbt clean` (preferred) {#remove-packages-and-compiled-files-as-part-of-dbt-clean} To remove packages as well as compiled files, include the value of your [packages-install-path](/reference/project-configs/packages-install-path) configuration in your `clean-targets` configuration.