Alerts config for source nodes defined in dbt_project.yml overrides the one defined in source.yml
Describe the bug
When creating dbt_sources (e.g. dbt run --target prod -d --select elementary.edr.dbt_artifacts.dbt_sources) wrong hierarchy order is applied when selecting source node meta.
alerts_config defined in dbt_project.yml overrides the one define in source.yaml... which shouldn't be the case. Meta should be used from source.yaml definition.
sources:
project:
+meta:
alerts_config:
channel: slack-channel
owner: [ "@owner" ]
sources:
- name: source
schema: sourceSchema
meta:
alerts_config:
channel: slack-channel
owner:
- "@owner"
tables:
- ...
To Reproduce Specify default meta in dbt_project.yml. Override it inside source.yaml. Try removing the default one.
Expected behavior
alerts_config defined in dbt_project.yaml overrides the one define in source.yaml... which shouldn't be the case. Meta should be used from source.yaml definition.
Environment (please complete the following information): dbt-core = "1.9.3" dbt-bigquery = "1.9.0" elementary-data = { version = "0.18.1", extras = ["bigquery"] }
This issue is stale because it has been open for too long with no activity. If you would like the issue to remain open, please remove the stale label or leave a comment.