Merge branch 'current' into dbt-teradata-1.6

.github/pull_request_template.md

@@ -10,7 +10,7 @@ To learn more about the writing conventions used in the dbt Labs docs, see the [
 <!--
 Uncomment if you're publishing docs for a prerelease version of dbt (delete if not applicable):
 - [ ] Add versioning components, as described in [Versioning Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
-- [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
+- [ ] Add a note to the prerelease version [Migration Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
 -->
 - [ ] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines.
 - [ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

website/blog/2021-11-23-how-to-upgrade-dbt-versions.md

@@ -62,7 +62,7 @@ As noted above, the project is on 0.16.0 right now. 0.17.2 is the final patch re
 >
 > Practically, it also lets you lock in "checkpoints" of known-stable setups. If you need to pause your migration work to deal with an urgent request, you can safely deploy what you've finished so far instead of having a bunch of unrelated half-finished changes.
 
-Review the migration guides to get an initial indication of what changes you might need to make. For example, in [the migration guide for 0.17.0](/guides/migration/versions), there are several significant changes to dbt's functionality, but it's unlikely that all of them will apply to your project. We'll cover this more later.
+Review the migration guides to get an initial indication of what changes you might need to make. For example, in [the migration guide for 0.17.0](/docs/dbt-versions/core-upgrade), there are several significant changes to dbt's functionality, but it's unlikely that all of them will apply to your project. We'll cover this more later.
 
 ## Step 2: `Add require-dbt-version` to your `dbt_project.yml` file.
 
@@ -126,9 +126,9 @@ In this case, our example project probably has dbt 0.3.0 installed. By reviewing
 
 ### Step 5b. Fix errors, then warnings
 
-Obviously, errors that stop you from running your dbt project at all are the most important to deal with. Let's assume that our project used a too-broadly-scoped variable in a macro file, support for which was removed in v0.17. The [migration guide explains what to do instead](/guides/migration/versions), and it's a pretty straightforward fix.
+Obviously, errors that stop you from running your dbt project at all are the most important to deal with. Let's assume that our project used a too-broadly-scoped variable in a macro file, support for which was removed in v0.17. The [migration guide explains what to do instead](/docs/dbt-versions/core-upgrade), and it's a pretty straightforward fix.
 
-Once your errors are out of the way, have a look at warnings. For example, 0.17 introduced `config-version: 2` to `dbt_project.yml`. Although it's backwards compatible for now, we know that support for the old version will be removed in a future version of dbt so we might as well deal with it now. Again, the migration guide explains [what we need to do](/guides/migration/versions), and how to take full advantage of the new functionality in the future.
+Once your errors are out of the way, have a look at warnings. For example, 0.17 introduced `config-version: 2` to `dbt_project.yml`. Although it's backwards compatible for now, we know that support for the old version will be removed in a future version of dbt so we might as well deal with it now. Again, the migration guide explains [what we need to do](/docs/dbt-versions/core-upgrade), and how to take full advantage of the new functionality in the future.
 
 ### Stay focused
 

website/blog/2022-05-03-making-dbt-cloud-api-calls-using-dbt-cloud-cli.md

@@ -12,6 +12,10 @@ date: 2022-05-03
 is_featured: true
 ---
 
+:::info Different from dbt Cloud CLI
+This blog explains how to use the `dbt-cloud-cli` Python library to create a data catalog app with dbt Cloud artifacts. This is different from the [dbt Cloud CLI](/docs/cloud/cloud-cli-installation), a tool that allows you to run dbt commands against your dbt Cloud development environment from your local command line.
+:::
+
 dbt Cloud is a hosted service that many organizations use for their dbt deployments. Among other things, it provides an interface for creating and managing deployment jobs. When triggered (e.g., cron schedule, API trigger), the jobs generate various artifacts that contain valuable metadata related to the dbt project and the run results.
 
 dbt Cloud provides a REST API for managing jobs, run artifacts and other dbt Cloud resources. Data/analytics engineers would often write custom scripts for issuing automated calls to the API using tools [cURL](https://curl.se/) or [Python Requests](https://requests.readthedocs.io/en/latest/).  In some cases, the engineers would go on and copy/rewrite them between projects that need to interact with the API. Now, they have a bunch of scripts on their hands that they need to maintain and develop further if business requirements change. If only there was a dedicated tool for interacting with the dbt Cloud API that abstracts away the complexities of the API calls behind an easy-to-use interface… Oh wait, there is: [the dbt-cloud-cli](https://github.com/data-mie/dbt-cloud-cli)!

website/blog/2022-08-31-august-product-update.md

@@ -22,7 +22,7 @@ You’ll hear more in [Tristan’s keynote](https://coalesce.getdbt.com/agenda/k
 
 ## **What's new**
 
-- **dbt Core v1.3 beta:** Do you use Python for analytics? The first beta prerelease of dbt Core v1.3—including support for dbt models written in Python—is [ready to explore](https://docs.getdbt.com/guides/migration/versions/upgrading-to-v1.3)! Check it out, and read more about dbt supported Python models [in our docs](/docs/build/python-models).
+- **dbt Core v1.3 beta:** Do you use Python for analytics? The first beta prerelease of dbt Core v1.3—including support for dbt models written in Python—is [ready to explore](https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.3)! Check it out, and read more about dbt supported Python models [in our docs](/docs/build/python-models).
 - **Technology Partner Program:** We just launched our new [Technology Partner Program](https://www.getdbt.com/blog/dbt-labs-technology-partner-program/) with 40+ friends in the Modern Data Stack to provide consistent support for seamless integrations joint-users can trust. Check our new [dbt Cloud integrations page](http://www.getdbt.com/product/integrations) for what’s available today!
 - **Single-tenant users:** dbt Cloud v1.1.60 is now available on dbt Cloud Enterprise.
 

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

@@ -28,7 +28,7 @@ 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](/guides/migration/versions)
+dbt v0.17.0. See the [migration guide](/docs/dbt-versions/core-upgrade)
 for more information on these changes.
 
 :::

website/docs/docs/cloud/cloud-cli-installation.md

@@ -270,4 +270,7 @@ If you have dbt Core installed locally, either:
 You can always uninstall the dbt Cloud CLI to return to using dbt Core.
 </details>
 
-
+<details>
+<summary>Why am I receiving a <code>Session occupied</code> error?</summary>
+If you've ran a dbt command and receive a <code>Session occupied</code> error, you can reattach to your existing session with <code>dbt reattach</code> and then press <code>Control-C</code> and choose to cancel the invocation.
+</details>

website/docs/docs/cloud/connect-data-platform/connect-databricks.md

@@ -26,6 +26,8 @@ Unity Catalog allows Databricks users to centrally manage all data assets, simpl
 
 To learn how to optimize performance with data platform-specific configurations in dbt Cloud, refer to [Databricks-specific configuration](/reference/resource-configs/databricks-configs).
 
+To grant users or roles database permissions (access rights and privileges), refer to the [example permissions](/reference/database-permissions/databricks-permissions) page.
+
 
 To set up the Databricks connection, supply the following fields:
 

website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md

@@ -64,3 +64,5 @@ The Bastion server should now be ready for dbt Cloud to use as a tunnel into the
 ## Configuration
 
 To learn how to optimize performance with data platform-specific configurations in dbt Cloud, refer to [Redshift-specific configuration](/reference/resource-configs/redshift-configs).
+
+To grant users or roles database permissions (access rights and privileges), refer to the [Redshift permissions](/reference/database-permissions/redshift-permissions) page or [Postgres permissions](/reference/database-permissions/postgres-permissions) page.

website/docs/docs/cloud/connect-data-platform/connect-snowflake.md

@@ -15,7 +15,7 @@ The following fields are required when creating a Snowflake connection
 | Warehouse | The virtual warehouse to use for running queries. | `transforming` |
 
 
-**Note:** A crucial part of working with dbt atop Snowflake is ensuring that users (in development environments) and/or service accounts (in deployment to production environments) have the correct permissions to take actions on Snowflake! Here is documentation of some [example permissions to configure Snowflake access](/reference/snowflake-permissions).
+**Note:** A crucial part of working with dbt atop Snowflake is ensuring that users (in development environments) and/or service accounts (in deployment to production environments) have the correct permissions to take actions on Snowflake! Here is documentation of some [example permissions to configure Snowflake access](/reference/database-permissions/snowflake-permissions).
 
 ### Username / Password
 

website/docs/docs/core/connect-data-platform/teradata-setup.md

@@ -244,4 +244,4 @@ The adapter was originally created by [Doug Beatty](https://github.com/dbeatty10
 
 ## License
 
-The adapter is published using Apache-2.0 License. Please see the link (ADD LINK HERE) for terms and conditions, such as creating derivative work and the support model. 
+The adapter is published using Apache-2.0 License. Refer to the [terms and conditions](https://github.com/dbt-labs/dbt-core/blob/main/License.md) to understand items such as creating derivative work and the support model. 

website/docs/docs/core/installation-overview.md

@@ -23,7 +23,7 @@ Most command-line tools, including dbt, have a `--help` flag that you can use to
 
 ## Upgrading dbt Core
 
-dbt provides a number of resources for understanding [general best practices](/blog/upgrade-dbt-without-fear) while upgrading your dbt project as well as detailed [migration guides](/guides/migration/versions/upgrading-to-v1.4) highlighting the changes required for each minor and major release, and [core versions](/docs/dbt-versions/core)
+dbt provides a number of resources for understanding [general best practices](/blog/upgrade-dbt-without-fear) while upgrading your dbt project as well as detailed [migration guides](/docs/dbt-versions/core-upgrade/upgrading-to-v1.4) highlighting the changes required for each minor and major release, and [core versions](/docs/dbt-versions/core)
 
 - [Upgrade Homebrew](/docs/core/homebrew-install#upgrading-dbt-and-your-adapter)
 - [Upgrade `pip`](/docs/core/pip-install#change-dbt-core-versions)

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

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

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

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

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

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

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

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

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

@@ -1,7 +1,14 @@
 ---
 title: "Upgrading to v1.4"
 description: New features and changes in dbt Core v1.4
+id: "upgrading-to-v1.4"
+displayed_sidebar: "docs"
 ---
+
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.4.latest/CHANGELOG.md)

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

@@ -1,7 +1,14 @@
 ---
 title: "Upgrading to v1.3"
 description: New features and changes in dbt Core v1.3
+id: "upgrading-to-v1.3"
+displayed_sidebar: "docs"
 ---
+
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.3.latest/CHANGELOG.md)

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

@@ -1,7 +1,14 @@
 ---
 title: "Upgrading to v1.2"
 description: New features and changes in dbt Core v1.2
+id: "upgrading-to-v1.2"
+displayed_sidebar: "docs"
 ---
+
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.2.latest/CHANGELOG.md)

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

@@ -1,7 +1,14 @@
 ---
 title: "Upgrading to v1.1"
 description: New features and changes in dbt Core v1.1
+id: "upgrading-to-v1.1"
+displayed_sidebar: "docs"
 ---
+
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/1.1.latest/CHANGELOG.md)

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

@@ -1,7 +1,14 @@
 ---
 title: "Upgrading to v1.0"
 description: New features and changes in dbt Core v1.0
+id: "upgrading-to-v1.0"
+displayed_sidebar: "docs"
 ---
+
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 ### Resources
 
 - [Discourse](https://discourse.getdbt.com/t/3180)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1,10 +1,16 @@
 ---
 title: "Upgrading to 0.15.0"
 id: "upgrading-to-0-15-0"
+displayed_sidebar: "docs"
 ---
 
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 The dbt v0.15.0 release contains a handful of breaking code changes for users upgrading from v0.14.0.
 
+
 ## Breaking changes
 
 ### Stricter YML compilation

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

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

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

@@ -1,9 +1,14 @@
 ---
 title: "Upgrading to 0.17.0"
 id: "upgrading-to-0-17-0"
+displayed_sidebar: "docs"
 
 ---
 
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 dbt v0.17.0 makes compilation more consistent, improves performance, and fixes a number of bugs.
 
 ## Articles:

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

@@ -1,8 +1,13 @@
 ---
 title: "Upgrading to 0.18.0"
+displayed_sidebar: "docs"
 
 ---
 
+import UpgradeMove from '/snippets/_upgrade-move.md';
+
+<UpgradeMove />
+
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/dev/marian-anderson/CHANGELOG.md)