From 8efd193b0c1f3f3f240008fa7a6c80eacc57d3ea Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 19 Sep 2024 09:13:36 +0100 Subject: [PATCH 1/2] Update behavior-changes.md adding redshift-restrict_direct_pg_catalog_access flag to yaml example per [slack thread](https://getdbt.slack.com/archives/C03SAHKKG2Z/p1726676174268999?thread_ts=1726623397.819369&cid=C03SAHKKG2Z) --- .../docs/reference/global-configs/behavior-changes.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index 4abdd7d2104..45e5fb6e0c9 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -41,7 +41,12 @@ By contrast, behavior change migrations happen slowly, over the course of months These flags _must_ be set in the `flags` dictionary in `dbt_project.yml`. They configure behaviors closely tied to project code, which means they should be defined in version control and modified through pull or merge requests, with the same testing and peer review. -The following example displays the current flags and their current default values in the latest dbt Cloud and dbt Core versions. To opt out of a specific behavior change, set the values of the flag to `False` in `dbt_project.yml`. You'll continue to see warnings for legacy behaviors that you have opted out of explicitly until you either resolve them (switch the flag to `True`) or choose to silence the warnings using the `warn_error_options.silence` flag. +The following example displays the current flags and their current default values in the latest dbt Cloud and dbt Core versions. To opt out of a specific behavior change, set the values of the flag to `False` in `dbt_project.yml`. You will continue to see warnings for legacy behaviors you’ve opted out of, until you either: + +- Resolve the issue (by switching the flag to `True`) +- Silence the warnings using the `warn_error_options.silence` flag + +Here is an example of the available behavior change flags with their default values: @@ -50,6 +55,7 @@ flags: require_explicit_package_overrides_for_builtin_materializations: False require_model_names_without_spaces: False source_freshness_run_project_hooks: False + restrict_direct_pg_catalog_access: False ``` @@ -61,7 +67,7 @@ When we use dbt Cloud in the following table, we're referring to accounts that h | require_explicit_package_overrides_for_builtin_materializations | 2024.04.141 | 2024.06.192 | 1.6.14, 1.7.14 | 1.8.0 | | require_resource_names_without_spaces | 2024.05.146 | TBD* | 1.8.0 | 1.9.0 | | source_freshness_run_project_hooks | 2024.03.61 | TBD* | 1.8.0 | 1.9.0 | -| [Redshift] restrict_direct_pg_catalog_access | 2024.09.242 | TBD* | dbt-redshift v1.9.0 | 1.9.0 | +| [Redshift] [restrict_direct_pg_catalog_access](#redshift-restrict_direct_pg_catalog_access) | 2024.09.242 | TBD* | dbt-redshift v1.9.0 | 1.9.0 | When the dbt Cloud Maturity is "TBD," it means we have not yet determined the exact date when these flags' default values will change. Affected users will see deprecation warnings in the meantime, and they will receive emails providing advance warning ahead of the maturity date. In the meantime, if you are seeing a deprecation warning, you can either: - Migrate your project to support the new behavior, and then set the flag to `True` to stop seeing the warnings. From 781d65623152879230c5aa3047ab6f1ba82b02e3 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 19 Sep 2024 13:14:31 +0100 Subject: [PATCH 2/2] Update website/docs/reference/global-configs/behavior-changes.md --- website/docs/reference/global-configs/behavior-changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index 45e5fb6e0c9..8e9e93b8488 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -46,7 +46,7 @@ The following example displays the current flags and their current default value - Resolve the issue (by switching the flag to `True`) - Silence the warnings using the `warn_error_options.silence` flag -Here is an example of the available behavior change flags with their default values: +Here's an example of the available behavior change flags with their default values: