Merge in the on_configuration_change config on relevant pages

website/docs/reference/model-configs.md

@@ -35,6 +35,7 @@ models:
   [<resource-path>](/reference/resource-configs/resource-path):
     [+](/reference/resource-configs/plus-prefix)[materialized](/reference/resource-configs/materialized): <materialization_name>
     [+](/reference/resource-configs/plus-prefix)[sql_header](/reference/resource-configs/sql_header): <string>
+    [+](/reference/resource-configs/plus-prefix)[on_configuration_change](/reference/resource-configs/on_configuration_change): apply | continue | fail #only for materialized views on supported adapters
 
 ```
 
@@ -55,6 +56,7 @@ models:
     config:
       [materialized](/reference/resource-configs/materialized): <materialization_name>
       [sql_header](/reference/resource-configs/sql_header): <string>
+      [on_configuration_change](/reference/resource-configs/on_configuration_change): apply | continue | fail #only for materialized views on supported adapters
 
 ```
 
@@ -72,6 +74,7 @@ models:
 {{ config(
     [materialized](/reference/resource-configs/materialized)="<materialization_name>",
     [sql_header](/reference/resource-configs/sql_header)="<string>"
+    [on_configuration_change](/reference/resource-configs/on_configuration_change): apply | continue | fail #only for materialized views for supported adapters
 ) }}
 
 ```

website/docs/reference/node-selection/defer.md

@@ -223,4 +223,5 @@ dbt will check to see if `dev_alice.model_a` exists. If it doesn't exist, dbt wi
 ## Related docs
 
 - [Using defer in dbt Cloud](/docs/cloud/about-cloud-develop-defer)
+- [on_configuration_change](/reference/resource-configs/on_configuration_change)
 

website/docs/reference/resource-configs/full_refresh.md

@@ -85,3 +85,6 @@ This logic is encoded in the [`should_full_refresh()`](https://github.com/dbt-la
 
 ## Recommendation
 Set `full_refresh: false` for models of especially large datasets, which you would _never_ want dbt to fully drop and recreate.
+
+## Reference docs
+* [on_configuration_change](/reference/resource-configs/on_configuration_change)

website/docs/reference/resource-configs/materialized.md

@@ -81,3 +81,14 @@ select ...
 
 You can also configure [custom materializations](/guides/create-new-materializations?step=1) in dbt. Custom materializations are a powerful way to extend dbt's functionality to meet your specific needs.
 
+## Creation Precedence
+<!-- This text is copied from /reference/resource-configs/on_configuration_change.md -->
+Materializations are implemented following this "drop through" life cycle:
+
+1. If a model does not exist with the provided path, create the new model.
+2. If a model exists, but has a different type, drop the existing model and create the new model.
+3. If [`--full-refresh`](/reference/resource-configs/full_refresh) is supplied, replace the existing model regardless of configuration changes and the [`on_configuration_change`](/reference/resource-configs/on_configuration_change) setting.
+4. If there are no configuration changes, perform the default action for that type (e.g. apply refresh for a materialized view).
+5. Determine whether to apply the configuration changes according to the `on_configuration_change` setting.
+
+

website/docs/reference/resource-configs/on_configuration_change.md

@@ -81,6 +81,6 @@ models:
 Materializations are implemented following this "drop through" life cycle:
 1. If a model does not exist with the provided path, create the new model.
 2. If a model exists, but has a different type, drop the existing model and create the new model. 
-3. If `--full-refresh` is supplied, replace the existing model regardless of configuration changes and the `on_configuration_change` setting.
+3. If [`--full-refresh`](/reference/resource-configs/full_refresh) is supplied, replace the existing model regardless of configuration changes and the `on_configuration_change` setting.
 4. If there are no configuration changes, perform the default action for that type (e.g. apply refresh for a materialized view).
 5. Determine whether to apply the configuration changes according to the `on_configuration_change` setting.