Set default values for enrichment toggles in project yaml #54
Labels
category:models
Related to the models in the package.
status:blocked
Maintainers can't work on this right now.
type:bug
Bugs or weaknesses. The issue has to contain steps to reproduce.
Issue
As of dbt v0.20, dbt started throwing warnings for tests associated with disabled models. An example of this was the page view enrichments models for Redshift. To mute the warning, the tests were set to be enabled using the same var used to enable the corresponding model:
dbt-snowplow-web/models/page_views/scratch/page_views_scratch.yml
Lines 285 to 288 in c0adfb1
These vars were defined in the packages
dbt_project.yml
file but could be over written in the root projectsdbt_project.yml
. Unfortunately a bug in dbt (dbt-labs/dbt-core#3698) meant that the value defined in the packages project yml file was incorrectly taking precedence over the value in the root project when the var was used in ayml
file such as thepage_views_scratch.yml
file outlined above.As a workaround in 0.5.0, all default values for these enrichment flags were set in var call itself.
dbt-snowplow-web/models/page_views/scratch/default/snowplow_web_pv_iab.sql
Line 5 in c0adfb1
This makes updating the default value a pain.
Solution
Once the underlying bug is fixed, revert to setting default values in the packages project file:
dbt-snowplow-web/dbt_project.yml
Lines 37 to 42 in c0adfb1
The text was updated successfully, but these errors were encountered: