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

Configuring a single model within dbt_project.yml #4888

Open
1 task done
dbeatty10 opened this issue Feb 9, 2024 · 0 comments
Open
1 task done

Configuring a single model within dbt_project.yml #4888

dbeatty10 opened this issue Feb 9, 2024 · 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

https://docs.getdbt.com/reference/model-configs#configuring-models and/or https://docs.getdbt.com/reference/source-configs#configuring-sources

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

Problem

Many people don't know how to drill all the way down to a single model/source within dbt_project.yml.

Proposed solution

Sources has this explainer:

image

dbt-labs/dbt-core#7128 (comment) reminds me that we should have something similar on the models page.

In particular, the config within dbt_project.yml for models is not intuitive for everyone:

models:
  **your_project_name**:
    subdirectory_1_name:
      subdirectory_2_name:
        **model_name**:
          +config_name: config_value

Sources are ever-so-slightly different:

sources:
  **your_project_name**:
    subdirectory_1_name:
      subdirectory_2_name:
        **source_name**:
          **source_table_name**:
            +config_name: config_value

Additional information

There might be other resource types that this applies to as well.

@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 Feb 9, 2024
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