Add support for creating bigquery labels from meta #890
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces a new feature flag,
labels_from_meta
, that allows adding labels from themeta
config intolabels
. If enabled,meta
labels are included alongside existinglabels
, withlabels
taking priority in case of conflicts.Default behavior remains unchanged unless the flag is explicitly set.
resolves #889
docs dbt-labs/docs.getdbt.com/#
Problem
Currently, users can add BigQuery labels through the explicit
labels
configuration, but there's no way to leverage existing metadata in themeta
field as labels. This creates duplicate work when users want to expose the same information in both places.Solution
Implemented a new
labels_from_meta
configuration flag that, when enabled, merges items from themeta
section with thelabels
configuration. This allows users to maintain a single source of information while still controlling which metadata is exposed as BigQuery labels.Key implementation details:
meta
values are included alongside existinglabels
labels
entries take precedenceChecklist