Updating notices across docs (#4722)

## What are you changing in this pull request and why? Deletes and otherwise alters older notices that are no longer needed, past their due date, or otherwise deprecated ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) so my content adheres to these guidelines. - [x] For [docs versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning), review how to [version a whole page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) and [version a block of content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content). - [x] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
dbt-labs · Jan 10, 2024 · 6b3fde3 · 6b3fde3
2 parents bcebadf + 6e54b25
commit 6b3fde3
Show file tree

Hide file tree

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

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

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

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

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

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

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

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

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

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

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

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

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

diff --git a/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-13-0.md b/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-13-0.md
@@ -4,10 +4,6 @@ id: "upgrading-to-0-13-0"
 displayed_sidebar: "docs"
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ## Breaking changes
 
 ### on-run-start and on-run-end

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

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

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

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

diff --git a/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-17-0.md b/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-17-0.md
@@ -5,10 +5,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 dbt v0.17.0 makes compilation more consistent, improves performance, and fixes a number of bugs.
 
 ## Articles:

diff --git a/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-18-0.md b/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-18-0.md
@@ -4,10 +4,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Changelog](https://github.com/dbt-labs/dbt-core/blob/dev/marian-anderson/CHANGELOG.md)

diff --git a/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-19-0.md b/...te/docs/docs/dbt-versions/core-upgrade/11-Older versions/upgrading-to-0-19-0.md
@@ -4,10 +4,6 @@ displayed_sidebar: "docs"
 
 ---
 
-import UpgradeMove from '/snippets/_upgrade-move.md';
-
-<UpgradeMove />
-
 ### Resources
 
 - [Discourse](https://discourse.getdbt.com/t/1951)

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

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

diff --git 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
-- 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.
+## 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
@@ -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
@@ -23,7 +23,6 @@ In this quickstart guide, you'll learn how to use dbt Cloud with BigQuery. It wi
 
 :::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
-Original file line number
+Diff line change
@@ Expand Up @@
     :::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.
     :::
@@ Expand Down @@