Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The + for configs ONLY applies to dbt_project.yml and not elsewhere #4693

Open
1 task done
dbeatty10 opened this issue Dec 22, 2023 · 0 comments
Open
1 task done

The + for configs ONLY applies to dbt_project.yml and not elsewhere #4693

dbeatty10 opened this issue Dec 22, 2023 · 0 comments
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear

Comments

@dbeatty10
Copy link
Contributor

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

At least these two pages:

What part(s) of the page would you like to see updated?

Note that we demarcate between a folder name and a configuration within dbt_project.yml by using a +.

The + for configs ONLY applies to dbt_project.yml under the corresponding resource key and does not apply to:

  1. config() Jinja macro within a resource file
  2. config property in a .yml file.

So we should include a short note similar to the one found here:

We demarcate between a folder name and a configuration by using a +, so marketing, paid_ads, and google below are folder names, whereas +materialized is a configuration being applied to those folder and all folders nested below them.
...

models:
  jaffle_shop:
    marketing:
      +materialized: view
      paid_ads:
        google:
          +materialized: table

Additional information

Context: dbt-labs/dbt-core#9314

@dbeatty10 dbeatty10 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear labels Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Development

No branches or pull requests

1 participant