We want to document and enforce stronger standards for how the dbt-jobs repository is laid out, so that teams don't have to decide for themselves and DE has more opportunities for automation.
This ticket tracks milestone M26.1 in the dbt roadmap.
Acceptance criteria
- A documented style guide on Wikitech standardizes:
- Semantics and naming conventions for models (e.g. what is staging, mart etc.).
- A folder structure for teams to use.
- Minimal required metadata for folders and models (e.g., contact information, visibility).
- contact information will be used to send job alerts (failures, delays, etc)
- How to document models and their columns.
- The default --vars that all models are expected to accept
- DE migrates all models to the standard.
Implementation notes
- We can review and take inspiration from dbt-core style guide and Brooklyn Data dbt coding conventions.