Project flags, for global config defaults + behavior change migrations

.github/pull_request_template.md

@@ -19,5 +19,5 @@ Uncomment when publishing docs for a prerelease version of dbt:
 Adding or removing pages (delete if not applicable):
 - [ ] Add/remove page in `website/sidebars.js`
 - [ ] Provide a unique filename for new pages
-- [ ] Add an entry for deleted pages in `website/static/_redirects`
+- [ ] Add an entry for deleted pages in `website/vercel.json`
 - [ ] Run link testing locally with `npm run build` to update the links that point to deleted pages

website/docs/docs/dbt-cloud-apis/sl-manifest.md

@@ -19,7 +19,7 @@ dbt creates an [artifact](/reference/artifacts/dbt-artifacts) file called the _S
 
 By using the semantic manifest produced by dbt Core, MetricFlow will instantiate a data flow plan and generate SQL from Semantic Layer query requests. It's a valuable reference that you can use to understand the structure and details of your data models.
 
-Similar to the [`manifest.json` file](/reference/artifacts/manifest-json), the `semantic_manifest.json` file also lives in the [target directory](/reference/project-configs/target-path) of your dbt project where dbt stores various artifacts (such as compiled models and tests) generated during the execution of your project.
+Similar to the [`manifest.json` file](/reference/artifacts/manifest-json), the `semantic_manifest.json` file also lives in the [target directory](/reference/global-configs/json-artifacts) of your dbt project where dbt stores various artifacts (such as compiled models and tests) generated during the execution of your project.
 
 ## How it's produced 
 

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

@@ -33,7 +33,7 @@ See GitHub discussion [dbt-labs/dbt-core#5468](https://github.com/dbt-labs/dbt-c
 - **[Metrics](/docs/build/build-metrics-intro)** now support an `expression` type (metrics-on-metrics), as well as a `metric()` function to use when referencing metrics from within models, macros, or `expression`-type metrics. For more information on how to use expression metrics, check out the [**`dbt_metrics` package**](https://github.com/dbt-labs/dbt_metrics)
 - **[dbt-Jinja functions](/reference/dbt-jinja-functions)** now include the [`itertools` Python module](/reference/dbt-jinja-functions/modules#itertools), as well as the [set](/reference/dbt-jinja-functions/set) and [zip](/reference/dbt-jinja-functions/zip) functions.
 - **[Node selection](/reference/node-selection/syntax)** includes a [file selection method](/reference/node-selection/methods#the-file-method) (`-s model.sql`), and [yaml selector](/reference/node-selection/yaml-selectors) inheritance.
-- **[Global configs](/reference/global-configs/about-global-configs)** now include CLI flag and environment variable settings for [`target-path`](/reference/project-configs/target-path) and [`log-path`](/reference/project-configs/log-path), which can be used to override the values set in `dbt_project.yml`
+- **[Global configs](/reference/global-configs/about-global-configs)** now include CLI flag and environment variable settings for [`target-path`](/reference/global-configs/json-artifacts) and [`log-path`](/reference/global-configs/logs), which can be used to override the values set in `dbt_project.yml`
 
 ### Specific adapters
 

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

@@ -70,7 +70,7 @@ Several under-the-hood changes from past minor versions, tagged with deprecation
 - Add [metrics](/docs/build/build-metrics-intro), a new node type
 - [Generic tests](/best-practices/writing-custom-generic-tests) can be defined in `tests/generic` (new), in addition to `macros/` (as before)
 - [Parsing](/reference/parsing): partial parsing and static parsing have been turned on by default.
-- [Global configs](/reference/global-configs/about-global-configs) have been standardized. Related updates to [global CLI flags](/reference/global-cli-flags) and [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml).
+- [Global configs](/reference/global-configs/about-global-configs) have been standardized. Related updates to [global CLI flags](/reference/global-configs/about-global-configs) and [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml).
 - [The `init` command](/reference/commands/init) has a whole new look and feel. It's no longer just for first-time users.
 - Add `result:<status>` subselectors for smarter reruns when dbt models have errors and tests fail. See examples: [Pro-tips for Workflows](/best-practices/best-practice-workflows#pro-tips-for-workflows)
 - Secret-prefixed [env vars](/reference/dbt-jinja-functions/env_var) are now allowed only in `profiles.yml` + `packages.yml`

website/docs/reference/artifacts/dbt-artifacts.md

@@ -30,7 +30,7 @@ Most dbt commands (and corresponding RPC methods) produce artifacts:
 
 ## Where are artifacts produced?
 
-By default, artifacts are written to the `/target` directory of your dbt project. You can configure the location using the [`target-path`](/reference/project-configs/target-path#configuration).
+By default, artifacts are written to the `/target` directory of your dbt project. You can configure the location using the [`target-path` flag](/reference/global-configs/json-artifacts).
 
 ## Common metadata
 

website/docs/reference/dbt_project.yml.md

@@ -42,8 +42,8 @@ The following example is a list of all available configurations in the `dbt_proj
 [docs-paths](/reference/project-configs/docs-paths): [directorypath]
 [asset-paths](/reference/project-configs/asset-paths): [directorypath]
 
-[target-path](/reference/project-configs/target-path): directorypath
-[log-path](/reference/project-configs/log-path): directorypath
+[target-path](/reference/global-configs/json-artifacts): directorypath
+[log-path](/reference/global-configs/logs): directorypath
 [packages-install-path](/reference/project-configs/packages-install-path): directorypath
 
 [clean-targets](/reference/project-configs/clean-targets): [directorypath]
@@ -52,6 +52,9 @@ The following example is a list of all available configurations in the `dbt_proj
 
 [require-dbt-version](/reference/project-configs/require-dbt-version): version-range | [version-range]
 
+[flags](/reference/global-configs/project-flags):
+  [<global-configs>](/reference/global-configs/project-flags)
+
 [dbt-cloud](/docs/cloud/cloud-cli-installation):
   [project-id](/docs/cloud/configure-cloud-cli#configure-the-dbt-cloud-cli): project_id # Required
   [defer-env-id](/docs/cloud/about-cloud-develop-defer#defer-in-dbt-cloud-cli): environment_id # Optional
@@ -120,8 +123,8 @@ vars:
 [docs-paths](/reference/project-configs/docs-paths): [directorypath]
 [asset-paths](/reference/project-configs/asset-paths): [directorypath]
 
-[target-path](/reference/project-configs/target-path): directorypath
-[log-path](/reference/project-configs/log-path): directorypath
+[target-path](/reference/global-configs/json-artifacts): directorypath
+[log-path](/reference/global-configs/logs): directorypath
 [packages-install-path](/reference/project-configs/packages-install-path): directorypath
 
 [clean-targets](/reference/project-configs/clean-targets): [directorypath]
@@ -193,8 +196,8 @@ vars:
 [docs-paths](/reference/project-configs/docs-paths): [directorypath]
 [asset-paths](/reference/project-configs/asset-paths): [directorypath]
 
-[target-path](/reference/project-configs/target-path): directorypath
-[log-path](/reference/project-configs/log-path): directorypath
+[target-path](/reference/global-configs/json-artifacts): directorypath
+[log-path](/reference/global-configs/logs): directorypath
 [packages-install-path](/reference/project-configs/packages-install-path): directorypath
 
 [clean-targets](/reference/project-configs/clean-targets): [directorypath]

website/docs/reference/events-logging.md

@@ -4,7 +4,7 @@ title: "Events and logs"
 
 As dbt runs, it generates events. The most common way to see those events is as log messages, written in real time to two places:
 - The command line terminal (`stdout`), to provide interactive feedback while running dbt.
-- The debug log file (`logs/dbt.log`), to enable detailed [debugging of errors](/guides/debug-errors) when they occur. The text-formatted log messages in this file include all `DEBUG`-level events, as well as contextual information, such as log level and thread name. The location of this file can be configured via [the `log_path` config](/reference/project-configs/log-path).
+- The debug log file (`logs/dbt.log`), to enable detailed [debugging of errors](/guides/debug-errors) when they occur. The text-formatted log messages in this file include all `DEBUG`-level events, as well as contextual information, such as log level and thread name. The location of this file can be configured via [the `log-path` flag](/reference/global-configs/logs).
 
 <File name='CLI'>