Question - Differences with dbt-jobs-as-code

[b-per]

Hi! 👋

Not an issue about the repo itself but I was wondering if you came across dbt-jobs-as-code beforehand and if there was a specific reason that led you to create this package?

I would just be keen to know if you wanted to use the other repo but something prevented you from using it due to the current feature set.

Cheers Benoit.

[pgoslatara]

Hey @b-per! Good question. So I built this repo before I found dbt-jobs-as-code, so that explains why I created this repo, also because I'd created something similar at a client and wanted to share a cleaner version unconstrained by some design choices necessary at the client.

dbt-jobs-as-code looks really nice, I've discussed it with a colleague at Xebia a while back, but there are some signs that make me hesitant about it:

• It's not available on pypi, makes it feel like a hobby project rather than something ready for production use.
• I've never seen any blog or presentation about a company using it.
• There's minimal activity in terms of PRs, releases and issues.
• No CI.

Nothing major, but it is stuff that as a consultant makes me hesitant to present dbt-jobs-as-code to a client.

In saying all that, internally at Xebia and during the webinars I've given, when I talk about dbt-cloud-jobs I always mention that this is a demo from me with the purpose of getting people to think about how they orchestrate dbt Cloud jobs (as I don't believe dbt Cloud offers any advise on this). I also mention that dbt will likely develop something suitable in the future and I very much see dbt-jobs-as-code as being capable of being this product give that it is way more feature-ful than anything I could build. What would be awesome is the ability to integrate this into dbt Cloud, so if there's a YML file with a certain name, then merges to main result in these jobs being created, but this is likely not something that can be implemented any time soon.

[b-per]

Hi again! Thanks for sending those details a few months ago!

I just wanted to mention that with your feedback, and after hearing some needs from dbt Cloud users, we have made a few improvements to dbt-jobs-as-code.

It is now in PyPi and has some (limited) testing in CI as well that runs for every PR and every weekend (so we get notified if it starts failing).

We also added some features to the tool:

• we can now restrict what projects/envs people want to target instead of looking at jobs across the account
• we added some templating capabilities, especially useful for people who want to "promote" jobs between different environments.

[pgoslatara]

Thanks @b-per for the update! Really happy to see this become more user-friendly in the hope of gaining adoption. Would be cool to publish a blog post on this to get it some wider attention.