Support config: in dbt_project.yml, in loco +

[jtcohen6]

Users find the + prefix very confusing. Its significance is unclear, it looks more special than it is, and many configs work equally well with and without it:

# dbt_project.yml
models:
  +materialized: view    # works
  installed_package:
    materialized: table  # also works

I don't want to get rid of the + prefix, since it's prevalent in our docs and across. Everything above should keep working. Instead, I'd like to make this the documented standard:

# dbt_project.yml
models:
  config:
    materialized: view
  installed_package:
    config:
      materialized: table

That would establish real consistency between dbt_project.yml and the syntax proposed in #2401 / added in #3616:

# models/whatever.yml
models:
  - name: my_model
    config:
      materialized: view

Questions

• Since config is a dictionary, do we need it to be +config?
• What if someone has a subdirectory or project named config? I'm willing to say... pick a different name.

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest; add a comment to notify the maintainers.