It is generally recommended to use a single git repository for dbt.
We should create on in the https://gitlab.wikimedia.org/repos/data-engineering group
It is generally recommended to use a single git repository for dbt.
We should create on in the https://gitlab.wikimedia.org/repos/data-engineering group
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Mayakp.wiki | T369226 [MI 1] Reporting, Data Visualization, and Data Communications | |||
| Resolved | Mayakp.wiki | T403304 [MI 1.2] Provide metric updates to staff through 2 metric-focused presentations | |||
| Resolved | Mayakp.wiki | T403305 Contributors Metrics Reporting for Staff and stakeholders | |||
| Resolved | Mayakp.wiki | T408146 [Hypothesis] WE1.5.1 Contributor metrics dashboard | |||
| Open | JMonton-WMF | T416679 dbt DPE work | |||
| Open | amastilovic | T406764 Provide a dbt-core development environment and production setup in the data-platform | |||
| Resolved | None | T406765 Create a new gitlab repository for use with dbt | |||
| Resolved | JMonton-WMF | T407322 Create dbt folder structure |
Suggestion: instead of naming the repo 'dbt' which looks a bit more like a fork of 'dbt', name it:
data-engineering/dbt-jobs
Or something like that?
This works for me, too.
Should we rename the repository before we get too many WIP branches?
I renamed it to dbt-jobs. The repo is renamed but the URL still uses dbt https://gitlab.wikimedia.org/repos/data-engineering/dbt
If you think it would be better, we could remove it and create it again. I believe there are only a couple of branches in progress and I could push the changes of those branches to the new repository.
Yesterday during a meeting, @amastilovic suggested dbt-models as name, I believe we agreed it is a good name. Is everyone else ok with this name? As I'm the only one having branches, I can rename the repo and the path and push the branches again.
cc @JAllemandou @Ottomata @BTullis
I don't think it's a bad name, but I'm wondering if it's not restrictive: in DBT, models are a specific thing, and since DBT also uses other concepts, I wonder if we shouldn't find a different name for this.
I like the dbt-jobs @Ottomata suggested earlier on.
I have renamed the path and name to dbt-jobs (https://gitlab.wikimedia.org/repos/data-engineering/dbt-jobs) for now. As we are the only ones working with this repository for now, we can decide later if we want to change to another name.
Maybe we end up finding a better name if we include more things in this repository.
We can keep the ticket open until we all agree on this.