Nest Exposure node `meta` under `config`
Housekeeping
- [X] I am a maintainer of dbt-core
Short description
The old/deprecated way of having meta was putting it directly on a node. However, awhile back we deprecated that paradigm and moved to nesting meta under a node's config. For reasoning I am not aware of, this never made it to Exposure nodes. We should begin supporting the "best practice" path
Acceptance criteria
- Exposure nodes have a meta property under their config property
- During parsing, flat meta specifications should end up under the
config.meta
Suggested Tests
- Exposure meta can be specified in the
dbt_project.yamlconfig specification - In an exposure definition, people can specify meta directly on an exposure or under a exposure's config, both should end up in the exposure's
config.meta
Impact to Other Teams
Change impacts Artifacts team (change to the artifacts)
Will backports be required?
No
Context
No response
@jtcohen6 I noticed on #7440 you mentioned in a comment that we intentionally didn't move meta under config for a subset of node types. Would you be able to speak to why that was? I know we did this intentionally, but without the context it at first looks like an inconsistency.
See also:
- https://github.com/dbt-labs/docs.getdbt.com/issues/3710