You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
Describe the feature
In the dbt_project.yml file you can pass specific config values to models based on the folder structure. This is extremely useful so that you are not forced to pass in the same value in individual file configs. This pattern however doesn't work for sources. A project.yml section that I would expect to work is as follows:
name: 'dbt'version: '1.0.0'config-version: 2
...
# This worksmodels:
dbt:
dir1:
+tags:
- fancy_tag1sub_dir1:
+enabled: falsesub_dir2:
+materialized: ephemeraldir2:
+tags:
- fancy_tag2# This doesn't cause an error but doesn't actually worksources:
dbt:
dir1:
+database:
- database_1sub_dir1:
+loaded_at_field: col_1sub_dir2:
+description: Sub_dir2 sources live heredir2:
+loader:
- Kafka
Describe alternatives you've considered
Just specifying the config in each source schema file
Who will this benefit?
Presumably any dbt users who have sources in separate files but those sources share config elements.
Are you interested in contributing this feature?
Potentially? If you get me started on which classes to work on
Anything else?
This is a duplicate of #2542, but it's already closed (this is not implemented as far as I can tell).
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
In the
dbt_project.yml
file you can pass specific config values to models based on the folder structure. This is extremely useful so that you are not forced to pass in the same value in individual file configs. This pattern however doesn't work for sources. A project.yml section that I would expect to work is as follows:Describe alternatives you've considered
Just specifying the config in each source schema file
Who will this benefit?
Presumably any dbt users who have sources in separate files but those sources share config elements.
Are you interested in contributing this feature?
Potentially? If you get me started on which classes to work on
Anything else?
This is a duplicate of #2542, but it's already closed (this is not implemented as far as I can tell).
The text was updated successfully, but these errors were encountered: