Code formatting fixes

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -18,7 +18,7 @@ body:
         For "big ideas" about future capabilities of dbt, we ask that you open a
         [discussion](https://github.com/dbt-labs/dbt-core/discussions) in the "Ideas" category instead.
       options:
-        - label: I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
+        - label: I have read the [expectations for open source contributors](https://docs.getdbt.com/community/resources/oss-expectations)
           required: true
         - label: I have searched the existing issues, and I could not find an existing issue for this feature
           required: true

.github/pull_request_template.md

@@ -16,7 +16,7 @@ resolves #
 ### Checklist
 
 - [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md) and understand what's expected of me
-- [ ] I have signed the [CLA](https://docs.getdbt.com/docs/contributor-license-agreements)
+- [ ] I have signed the [CLA](https://docs.getdbt.com/community/resources/contributor-license-agreements)
 - [ ] I have run this code in development and it appears to resolve the stated issue
 - [ ] This PR includes tests, or tests are not required/relevant for this PR
 - [ ] I have [opened an issue to add/update docs](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose), or docs changes are not required/relevant for this PR

CONTRIBUTING.md

@@ -13,7 +13,7 @@
 
 ## About this document
 
-There are many ways to contribute to the ongoing development of `dbt-core`, such as by participating in discussions and issues. We encourage you to first read our higher-level document: ["Expectations for Open Source Contributors"](https://docs.getdbt.com/docs/contributing/oss-expectations).
+There are many ways to contribute to the ongoing development of `dbt-core`, such as by participating in discussions and issues. We encourage you to first read our higher-level document: ["Expectations for Open Source Contributors"](https://docs.getdbt.com/community/resources/oss-expectations).
 
 The rest of this document serves as a more granular guide for contributing code changes to `dbt-core` (this repository). It is not intended as a guide for using `dbt-core`, and some pieces assume a level of familiarity with Python development (virtualenvs, `pip`, etc). Specific code snippets in this guide assume you are using macOS or Linux and are comfortable with the command line.
 
@@ -21,8 +21,8 @@ If you get stuck, we're happy to help! Drop us a line in the `#dbt-core-developm
 
 ### Notes
 
-- **Adapters:** Is your issue or proposed code change related to a specific [database adapter](https://docs.getdbt.com/docs/available-adapters)? If so, please open issues, PRs, and discussions in that adapter's repository instead. The sole exception is Postgres; the `dbt-postgres` plugin lives in this repository (`dbt-core`).
-- **CLA:** Please note that anyone contributing code to `dbt-core` must sign the [Contributor License Agreement](https://docs.getdbt.com/docs/contributor-license-agreements). If you are unable to sign the CLA, the `dbt-core` maintainers will unfortunately be unable to merge any of your Pull Requests. We welcome you to participate in discussions, open issues, and comment on existing ones.
+- **Adapters:** Is your issue or proposed code change related to a specific [database adapter](https://docs.getdbt.com/docs/supported-data-platforms)? If so, please open issues, PRs, and discussions in that adapter's repository instead. The sole exception is Postgres; the `dbt-postgres` plugin lives in this repository (`dbt-core`).
+- **CLA:** Please note that anyone contributing code to `dbt-core` must sign the [Contributor License Agreement](https://docs.getdbt.com/community/resources/contributor-license-agreements). If you are unable to sign the CLA, the `dbt-core` maintainers will unfortunately be unable to merge any of your Pull Requests. We welcome you to participate in discussions, open issues, and comment on existing ones.
 - **Branches:** All pull requests from community contributors should target the `main` branch (default). If the change is needed as a patch for a minor version of dbt that has already been released (or is already a release candidate), a maintainer will backport the changes in your PR to the relevant "latest" release branch (`1.0.latest`, `1.1.latest`, ...). If an issue fix applies to a release branch, that fix should be first committed to the development branch and then to the release branch (rarely release-branch fixes may not apply to `main`).
 - **Releases**: Before releasing a new minor version of Core, we prepare a series of alphas and release candidates to allow users (especially employees of dbt Labs!) to test the new version in live environments. This is an important quality assurance step, as it exposes the new code to a wide variety of complicated deployments and can surface bugs before official release. Releases are accessible via pip, homebrew, and dbt Cloud.
 
@@ -113,7 +113,7 @@ When installed in this way, any changes you make to your local copy of the sourc
 
 With your virtualenv activated, the `dbt` script should point back to the source code you've cloned on your machine. You can verify this by running `which dbt`. This command should show you a path to an executable in your virtualenv.
 
-Configure your [profile](https://docs.getdbt.com/docs/configure-your-profile) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate.
+Configure your [profile](https://docs.getdbt.com/docs/core/connection-profiles) as necessary to connect to your target databases. It may be a good idea to add a new profile pointing to a local Postgres instance, or a specific test sandbox within your data warehouse if appropriate.
 
 ## Testing
 

README.md

@@ -15,14 +15,14 @@
 
 Analysts using dbt can transform their data by simply writing select statements, while dbt handles turning these statements into tables and views in a data warehouse.
 
-These select statements, or "models", form a dbt project. Models frequently build on top of one another – dbt makes it easy to [manage relationships](https://docs.getdbt.com/docs/ref) between models, and [visualize these relationships](https://docs.getdbt.com/docs/documentation), as well as assure the quality of your transformations through [testing](https://docs.getdbt.com/docs/testing).
+These select statements, or "models", form a dbt project. Models frequently build on top of one another – dbt makes it easy to [manage relationships](https://docs.getdbt.com/reference/dbt-jinja-functions/ref) between models, and [visualize these relationships](https://docs.getdbt.com/docs/collaborate/documentation), as well as assure the quality of your transformations through [testing](https://docs.getdbt.com/docs/build/tests).
 
 ![dbt dag](https://raw.githubusercontent.com/dbt-labs/dbt-core/6c6649f9129d5d108aa3b0526f634cd8f3a9d1ed/etc/dbt-dag.png)
 
 ## Getting started
 
 - [Install dbt](https://docs.getdbt.com/docs/get-started/installation)
-- Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/docs/about/viewpoint/)
+- Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/community/resources/viewpoint)
 
 ## Join the dbt Community
 

core/README.md

@@ -15,14 +15,14 @@
 
 Analysts using dbt can transform their data by simply writing select statements, while dbt handles turning these statements into tables and views in a data warehouse.
 
-These select statements, or "models", form a dbt project. Models frequently build on top of one another – dbt makes it easy to [manage relationships](https://docs.getdbt.com/docs/ref) between models, and [visualize these relationships](https://docs.getdbt.com/docs/documentation), as well as assure the quality of your transformations through [testing](https://docs.getdbt.com/docs/testing).
+These select statements, or "models", form a dbt project. Models frequently build on top of one another – dbt makes it easy to [manage relationships](https://docs.getdbt.com/reference/dbt-jinja-functions/ref) between models, and [visualize these relationships](https://docs.getdbt.com/docs/collaborate/documentation), as well as assure the quality of your transformations through [testing](https://docs.getdbt.com/docs/build/tests).
 
 ![dbt dag](https://raw.githubusercontent.com/dbt-labs/dbt-core/6c6649f9129d5d108aa3b0526f634cd8f3a9d1ed/etc/dbt-dag.png)
 
 ## Getting started
 
-- [Install dbt](https://docs.getdbt.com/docs/installation)
-- Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/docs/about/viewpoint/)
+- [Install dbt](https://docs.getdbt.com/docs/core/installation)
+- Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/community/resources/viewpoint)
 
 ## Join the dbt Community
 

core/dbt/config/project.py

@@ -69,7 +69,7 @@ The packages.yml file in this project is malformed. Please double check
 the contents of this file and fix any errors before retrying.
 
 You can find more information on the syntax for this file here:
-https://docs.getdbt.com/docs/package-management
+https://docs.getdbt.com/docs/build/packages
 
 Validator Error:
 {error}

core/dbt/config/selectors.py

@@ -21,7 +21,7 @@ The selectors.yml file in this project is malformed. Please double check
 the contents of this file and fix any errors before retrying.
 
 You can find more information on the syntax for this file here:
-https://docs.getdbt.com/docs/package-management
+https://docs.getdbt.com/docs/build/packages
 
 Validator Error:
 {error}

core/dbt/constants.py

@@ -5,6 +5,4 @@ METADATA_ENV_PREFIX = "DBT_ENV_CUSTOM_ENV_"
 MAXIMUM_SEED_SIZE = 1 * 1024 * 1024
 MAXIMUM_SEED_SIZE_NAME = "1MB"
 
-PIN_PACKAGE_URL = (
-    "https://docs.getdbt.com/docs/package-management#section-specifying-package-versions"
-)
+PIN_PACKAGE_URL = "https://docs.getdbt.com/docs/build/packages#section-specifying-package-versions"

core/dbt/deps/README.md

@@ -1,11 +1,11 @@
 # Deps README
 
-The deps module is responsible for installing dbt packages into dbt projects.  A dbt package is a standalone dbt project with models and macros that solve a specific problem area.  More specific information on dbt packages is available on the [docs site](https://docs.getdbt.com/docs/building-a-dbt-project/package-management).
+The deps module is responsible for installing dbt packages into dbt projects.  A dbt package is a standalone dbt project with models and macros that solve a specific problem area.  More specific information on dbt packages is available on the [docs site](https://docs.getdbt.com/docs/build/packages).
 
 
 # What's a package?
 
-See [How do I specify a package?](https://docs.getdbt.com/docs/building-a-dbt-project/package-management#how-do-i-specify-a-package) on the docs site for a detailed explination of the different types of packages supported and expected formats.
+See [How do I specify a package?](https://docs.getdbt.com/docs/build/packages#how-do-i-specify-a-package) on the docs site for a detailed explination of the different types of packages supported and expected formats.
 
 
 # Files

core/dbt/events/types.py

@@ -130,7 +130,7 @@ class LogDbtProfileError(ErrorLevel):
         msg += """
 For more information on configuring profiles, please consult the dbt docs:
 
-https://docs.getdbt.com/docs/configure-your-profile
+https://docs.getdbt.com/docs/core/connection-profiles
 """
         return msg
 
@@ -305,7 +305,7 @@ class AdapterDeprecationWarning(WarnLevel):
             f"The adapter function `adapter.{self.old_name}` is deprecated and will be removed in "
             f"a future release of dbt. Please use `adapter.{self.new_name}` instead. "
             f"\n\nDocumentation for {self.new_name} can be found here:"
-            f"\n\nhttps://docs.getdbt.com/docs/adapter"
+            f"\n\nhttps://docs.getdbt.com/reference/dbt-jinja-functions/adapter"
         )
         return line_wrap_message(warning_tag(f"Deprecated functionality\n\n{description}"))
 
@@ -2060,7 +2060,7 @@ class EnsureGitInstalled(ErrorLevel):
         return (
             "Make sure git is installed on your machine. More "
             "information: "
-            "https://docs.getdbt.com/docs/package-management"
+            "https://docs.getdbt.com/docs/build/packages"
         )
 
 

core/dbt/include/global_project/docs/overview.md

@@ -27,7 +27,7 @@ button at the top-right of this lineage pane, you'll be able to see all of the m
 or are built from, the model you're exploring.
 
 Once expanded, you'll be able to use the `--select` and `--exclude` model selection syntax to filter the
-models in the graph. For more information on model selection, check out the [dbt docs](https://docs.getdbt.com/docs/model-selection-syntax).
+models in the graph. For more information on model selection, check out the [dbt docs](https://docs.getdbt.com/reference/node-selection/syntax).
 
 Note that you can also right-click on models to interactively filter and explore the graph.
 
@@ -36,8 +36,8 @@ Note that you can also right-click on models to interactively filter and explore
 ### More information
 
 - [What is dbt](https://docs.getdbt.com/docs/introduction)?
-- Read the [dbt viewpoint](https://docs.getdbt.com/docs/viewpoint)
-- [Installation](https://docs.getdbt.com/docs/installation)
+- Read the [dbt viewpoint](https://docs.getdbt.com/community/resources/viewpoint)
+- [Installation](https://docs.getdbt.com/docs/core/installation)
 - Join the [dbt Community](https://www.getdbt.com/community/) for questions and discussion
 
 {% enddocs %}

core/dbt/include/starter_project/dbt_project.yml

@@ -25,7 +25,7 @@ clean-targets:         # directories to be removed by `dbt clean`
 
 
 # Configuring models
-# Full documentation: https://docs.getdbt.com/docs/configuring-models
+# Full documentation: https://docs.getdbt.com/reference/model-configs
 
 # In this example config, we tell dbt to build all models in the example/
 # directory as views. These settings can be overridden in the individual model

core/dbt/links.py

@@ -1,4 +1,6 @@
-ProfileConfigDocs = "https://docs.getdbt.com/docs/configure-your-profile"
-SnowflakeQuotingDocs = "https://docs.getdbt.com/v0.10/docs/configuring-quoting"
-IncrementalDocs = "https://docs.getdbt.com/docs/configuring-incremental-models"
-BigQueryNewPartitionBy = "https://docs.getdbt.com/docs/upgrading-to-0-16-0"
+ProfileConfigDocs = "https://docs.getdbt.com/docs/core/connection-profiles"
+SnowflakeQuotingDocs = "https://docs.getdbt.com/reference/project-configs/quoting"
+IncrementalDocs = "https://docs.getdbt.com/docs/build/incremental-models"
+BigQueryNewPartitionBy = (
+    "https://docs.getdbt.com/guides/migration/versions/Older%20versions/upgrading-to-0-16-0"
+)

core/dbt/task/init.py

@@ -37,7 +37,7 @@ from dbt.include.global_project import PROJECT_NAME as GLOBAL_PROJECT_NAME
 
 from dbt.task.base import BaseTask, move_to_nearest_project_dir
 
-DOCS_URL = "https://docs.getdbt.com/docs/configure-your-profile"
+DOCS_URL = "https://docs.getdbt.com/docs/core/connection-profiles"
 SLACK_URL = "https://community.getdbt.com/"
 
 # This file is not needed for the starter project but exists for finding the resource path
@@ -224,7 +224,7 @@ class InitTask(BaseTask):
         prompt_msg = (
             "Which database would you like to use?\n"
             + "\n".join([f"[{n+1}] {v}" for n, v in enumerate(available_adapters)])
-            + "\n\n(Don't see the one you want? https://docs.getdbt.com/docs/available-adapters)"
+            + "\n\n(Don't see the one you want? https://docs.getdbt.com/docs/supported-data-platforms)"
             + "\n\nEnter a number"
         )
         numeric_choice = click.prompt(prompt_msg, type=click.INT)
@@ -281,7 +281,9 @@ class InitTask(BaseTask):
         # create a new project and set up the user's profile.
         available_adapters = list(_get_adapter_plugin_names())
         if not len(available_adapters):
-            print("No adapters available. Go to https://docs.getdbt.com/docs/available-adapters")
+            print(
+                "No adapters available. Go to https://docs.getdbt.com/docs/supported-data-platforms"
+            )
             sys.exit(1)
         project_name = self.get_valid_project_name()
         project_path = Path(project_name)

core/dbt/version.py

@@ -74,7 +74,7 @@ def _get_core_msg_lines(installed, latest) -> Tuple[List[List[str]], str]:
         update_info = (
             "  Your version of dbt-core is out of date!\n"
             "  You can find instructions for upgrading here:\n"
-            "  https://docs.getdbt.com/docs/installation"
+            "  https://docs.getdbt.com/docs/core/installation"
         )
 
     return [
@@ -114,7 +114,7 @@ def _get_plugins_msg(installed: dbt.semver.VersionSpecifier) -> str:
         update_msg = (
             "  At least one plugin is out of date or incompatible with dbt-core.\n"
             "  You can find instructions for upgrading here:\n"
-            "  https://docs.getdbt.com/docs/installation"
+            "  https://docs.getdbt.com/docs/core/installation"
         )
         msg_lines += ["", update_msg]
 

docs/roadmap/2022-05-dbt-a-core-story.md

@@ -63,7 +63,7 @@ It's true that many of the people now building dbt aren't themselves users of it
 
 Welcome to the official program for "dbt: A Core Story," the devised theatre piece where everyone has a part to play. First, a few housekeeping items.
 
-We'll be releasing a new minor version of dbt Core every 3 months: April, July, August, January (2023). We put out our new [adapter](https://docs.getdbt.com/docs/available-adapters) versions at the same time. Adapters maintained by other people might be available for upgrade a few weeks later. For each new minor version, we put up a ["migration guide"](https://docs.getdbt.com/docs/guides/migration-guide) in the docs.
+We'll be releasing a new minor version of dbt Core every 3 months: April, July, August, January (2023). We put out our new [adapter](https://docs.getdbt.com/docs/supported-data-platforms) versions at the same time. Adapters maintained by other people might be available for upgrade a few weeks later. For each new minor version, we put up a ["migration guide"](https://docs.getdbt.com/guides/migration/versions) in the docs.
 
 Everything we work on is public on GitHub. I attach issues to [milestones](https://github.com/dbt-labs/dbt-core/milestones) for upcoming releases. We're using [discussions](https://github.com/dbt-labs/dbt-core/discussions) now for bigger-picture conversations—stuff we're thinking about, even if we can't write the code for it right away. If the dbt Community Slack feels overwhelming, discussions still feel, for now, like a slower-paced forum for dreaming up ideas, talking through caveats and rough edges. I really welcome your voices there.
 
@@ -91,7 +91,7 @@ At the same time, I was learning a **ton** about dbt—what it is today, what it
 
 So, for both reasons, I've been sharing the load with the engineering team building dbt Core. This requires more time, and process, but it also requires a level of rigor and organization that I didn't have when it was just me. Bugs don't get lost in the shuffle, and get resolved more quickly.
 
-Is this groundbreaking stuff? No, but it is major-version-one stuff. Is every one of these issues game-changing? No, but they matter a lot to the person who opens them—and I believe it matters a lot to you, a person who has invested meaningfully in standardizing on dbt Core. You should want to know that that core dbt functionality is well maintained, to know that when you run into a bug or have an idea there will be a human on the other end to receive and respond to it. To that end, I want to share a new doc we put together over the past few months: [Expectations for OSS Contributors](https://docs.getdbt.com/docs/contributing/oss-expectations).
+Is this groundbreaking stuff? No, but it is major-version-one stuff. Is every one of these issues game-changing? No, but they matter a lot to the person who opens them—and I believe it matters a lot to you, a person who has invested meaningfully in standardizing on dbt Core. You should want to know that that core dbt functionality is well maintained, to know that when you run into a bug or have an idea there will be a human on the other end to receive and respond to it. To that end, I want to share a new doc we put together over the past few months: [Expectations for OSS Contributors](https://docs.getdbt.com/community/resources/oss-expectations).
 
 It took some doing, but we now live in a world where:
 - every issue gets a timely response
@@ -102,7 +102,7 @@ I care about making contribution accessible, and making dbt a thing we can keep
 
 ### Scene 3: v1.1 (Gloria Casarez)
 
-At the end of April, [we released v1.1](https://github.com/dbt-labs/dbt-core/releases/tag/v1.1.0), named for Gloria Casarez, the activist and advocate for the rights of LGBTQ+ people in Philadelphia. This release had [some good stuff in it](https://docs.getdbt.com/docs/guides/migration-guide/upgrading-to-v1.1), including a few boundary-pushing community contributions—but I'll be the first to admit that it was a lighter release than others in recent memory. The biggest work was sharpening our tools, and sharpening the team. We'd rather do this work upfront, so we can build and ship the bigger stuff, with alacrity and assurance.
+At the end of April, [we released v1.1](https://github.com/dbt-labs/dbt-core/releases/tag/v1.1.0), named for Gloria Casarez, the activist and advocate for the rights of LGBTQ+ people in Philadelphia. This release had [some good stuff in it](https://docs.getdbt.com/guides/migration/versions/upgrading-to-v1.1), including a few boundary-pushing community contributions—but I'll be the first to admit that it was a lighter release than others in recent memory. The biggest work was sharpening our tools, and sharpening the team. We'd rather do this work upfront, so we can build and ship the bigger stuff, with alacrity and assurance.
 
 ## Act II: Ergonomic interfaces (May–July)
 
@@ -128,7 +128,7 @@ If you've hung around the `dbt-core` GitHub repo lately, you may have seen that
 
 Not long ago, we had one team (one person), one codebase, one tightly coupled application that did all of the things, from beginning to end, without clear stopping points in the middle. Now, I'm truly lucky to work with a team of talented software engineers, as we try to make the experience of developing and interfacing with `dbt-core` as no-bs as it is to use. We believe the highest-leverage way to do this is by splitting up the team into specialties, and the codebase into modular interfaces.
 
-For too long now, the [docs for dbt's "Python API"](https://docs.getdbt.com/docs/running-a-dbt-project/dbt-api) have cautioned:
+For too long now, we have cautioned:
 
 > It _is_ possible to import and invoke dbt as a Python module. This API is still not contracted or documented, and it is liable to change in future versions of `dbt-core` without warning. Please use caution when upgrading across versions of dbt if you choose to run dbt in this manner!
 

docs/roadmap/2022-08-back-for-more.md

@@ -46,7 +46,7 @@ Hopefully, you're already well aware of, and happily making use of, the capabili
 
 I got to see a very small number of you a few months ago at a London dbt meetup, where I presented May's edition of roadmap. I'm looking forward—we're all (!) looking forward—to seeing and talking with many more of you in October for [Coalesce](https://coalesce.getdbt.com/). For those who are able and comfortable to make the trip to New Orleans, London, or Sydney—and for all the many more who are planning on a "classic Coalesce" experience, from the comfort of your laptop—we're very excited to have you.
 
-The big thing coming in dbt Core v1.3 is support for Python models. You already knew that. All the details are in [the beta docs](https://docs.getdbt.com/docs/building-a-dbt-project/building-models/python-models), so give 'em a read now if you haven't yet.
+The big thing coming in dbt Core v1.3 is support for Python models. You already knew that. All the details are in [the beta docs](https://docs.getdbt.com/docs/build/python-models), so give 'em a read now if you haven't yet.
 
 There are a couple of FAQs (Frequently Associated Qualms) that I want to address, here and now, in case you're thinking one of them:
 

plugins/postgres/README.md

@@ -14,12 +14,12 @@ dbt is the T in ELT. Organize, cleanse, denormalize, filter, rename, and pre-agg
 ## dbt-postgres
 
 The `dbt-postgres` package contains all of the code enabling dbt to work with a Postgres database. For
-more information on using dbt with Postgres, consult [the docs](https://docs.getdbt.com/docs/profile-postgres).
+more information on using dbt with Postgres, consult [the docs](https://docs.getdbt.com/reference/warehouse-setups/postgres-setup).
 
 ## Getting started
 
-- [Install dbt](https://docs.getdbt.com/docs/installation)
-- Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/docs/about/viewpoint/)
+- [Install dbt](https://docs.getdbt.com/docs/core/installation)
+- Read the [introduction](https://docs.getdbt.com/docs/introduction/) and [viewpoint](https://docs.getdbt.com/community/resources/viewpoint)
 
 ## Join the dbt Community
 

tests/adapter/README.md

@@ -4,7 +4,7 @@
 
 # dbt-tests-adapter
 
-For context and guidance on using this package, please read: ["Testing a new adapter"](https://docs.getdbt.com/docs/contributing/testing-a-new-adapter)
+For context and guidance on using this package, please read: ["Testing a new adapter"](https://docs.getdbt.com/guides/dbt-ecosystem/adapter-development/4-testing-a-new-adapter)
 
 ## What is it?
 
@@ -31,7 +31,7 @@ To install:
 pip install dbt-tests-adapter
 ```
 
-This package is versioned in lockstep with `dbt-core`, and [the same versioning guidelines](https://docs.getdbt.com/docs/core-versions) apply:
+This package is versioned in lockstep with `dbt-core`, and [the same versioning guidelines](https://docs.getdbt.com/docs/dbt-versions/core) apply:
 - New "basic" test cases MAY be added in minor versions ONLY. They may not be included in patch releases.
 - Breaking changes to existing test cases MAY be included and communicated as part of minor version upgrades ONLY. They MAY NOT be included in patch releases. We will aim to avoid these whenever possible.
 - New "optional" test cases, and non-breaking fixes to existing test cases, MAY be added in minor or patch versions.

tests/functional/init/test_init.py

@@ -39,7 +39,7 @@ class TestInitProjectWithExistingProfilesYml:
                     f"The profile test already exists in {os.path.join(project.profiles_dir, 'profiles.yml')}. Continue and overwrite it?"
                 ),
                 call.prompt(
-                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/available-adapters)\n\nEnter a number",
+                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/supported-data-platforms)\n\nEnter a number",
                     type=click.INT,
                 ),
                 call.prompt(
@@ -116,7 +116,7 @@ class TestInitProjectWithoutExistingProfilesYml:
         manager.assert_has_calls(
             [
                 call.prompt(
-                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/available-adapters)\n\nEnter a number",
+                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/supported-data-platforms)\n\nEnter a number",
                     type=click.INT,
                 ),
                 call.prompt(
@@ -187,7 +187,7 @@ class TestInitProjectWithoutExistingProfilesYmlOrTemplate:
         manager.assert_has_calls(
             [
                 call.prompt(
-                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/available-adapters)\n\nEnter a number",
+                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/supported-data-platforms)\n\nEnter a number",
                     type=click.INT,
                 ),
             ]
@@ -341,7 +341,7 @@ class TestInitInvalidProfileTemplate:
                     f"The profile test already exists in {os.path.join(project.profiles_dir, 'profiles.yml')}. Continue and overwrite it?"
                 ),
                 call.prompt(
-                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/available-adapters)\n\nEnter a number",
+                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/supported-data-platforms)\n\nEnter a number",
                     type=click.INT,
                 ),
                 call.prompt(
@@ -457,7 +457,7 @@ class TestInitOutsideOfProject(TestInitOutsideOfProjectBase):
             [
                 call.prompt("Enter a name for your project (letters, digits, underscore)"),
                 call.prompt(
-                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/available-adapters)\n\nEnter a number",
+                    "Which database would you like to use?\n[1] postgres\n\n(Don't see the one you want? https://docs.getdbt.com/docs/supported-data-platforms)\n\nEnter a number",
                     type=click.INT,
                 ),
                 call.prompt(
@@ -553,7 +553,7 @@ clean-targets:         # directories to be removed by `dbt clean`
 
 
 # Configuring models
-# Full documentation: https://docs.getdbt.com/docs/configuring-models
+# Full documentation: https://docs.getdbt.com/reference/model-configs
 
 # In this example config, we tell dbt to build all models in the example/
 # directory as views. These settings can be overridden in the individual model
@@ -672,7 +672,7 @@ clean-targets:         # directories to be removed by `dbt clean`
 
 
 # Configuring models
-# Full documentation: https://docs.getdbt.com/docs/configuring-models
+# Full documentation: https://docs.getdbt.com/reference/model-configs
 
 # In this example config, we tell dbt to build all models in the example/
 # directory as views. These settings can be overridden in the individual model

tests/unit/test_version.py

@@ -74,7 +74,7 @@ class TestGetVersionInformation:
                 "",
                 "  Your version of dbt-core is out of date!",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "Plugins:",
                 f"  - foobar: 1.0.0 - {green('Up to date!')}",
@@ -241,7 +241,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -271,7 +271,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -301,7 +301,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -331,7 +331,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -361,7 +361,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -391,7 +391,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -421,7 +421,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -451,7 +451,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -481,7 +481,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -511,7 +511,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]
@@ -551,7 +551,7 @@ class TestGetVersionInformation:
                 "",
                 "  At least one plugin is out of date or incompatible with dbt-core.",
                 "  You can find instructions for upgrading here:",
-                "  https://docs.getdbt.com/docs/installation",
+                "  https://docs.getdbt.com/docs/core/installation",
                 "",
                 "",
             ]