dbt-labs / dbt-labs/docs.getdbt.com
When replacing a package node with your own model, its configs are kept
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 1.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 130
Description
### Contributions
- [x] I have read the contribution docs, and understand what's expected of me.
### Background content
See [this internal Slack thread](https://dbt-labs.slack.com/archives/C05FWBP9X1U/p1773245283896419) to make sure this update is even relevant or not.
### Link to the page on docs.getdbt.com requiring updates
Maybe one or more of these?
- https://docs.getdbt.com/reference/resource-configs/enabled
- https://docs.getdbt.com/docs/build/packages
- https://docs.getdbt.com/reference/configs-and-properties
Maybe somewhere else?
### What part(s) of the page would you like to see updated?
Context here:
https://github.com/dbt-labs/dbt-core/issues/12243#issuecomment-4008125213
Namely:
- Any configs from the package node are applied to the [model or seed or snapshot you put in its place](https://docs.getdbt.com/reference/resource-configs/enabled#disable-a-model-in-a-package-in-order-to-use-your-own-version-of-the-model)
- There's no way to override its configs or properties in `dbt_project.yml` or `seeds/_properties.yml` files
### Additional information
See here for a workaround:
- https://github.com/dbt-labs/docs.getdbt.com/issues/5094
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.