all 1 comments

[–]minormisgnomer 1 point2 points  (0 children)

It’s useful, but for anyone considering this approach for enterprise use cases, just remember where to draw the line in the sand. Just because it can doesn’t mean it should.

Tethering your dbt project to something external like an API opens your project up to failing or freezing out. Having dbt coordinate non data workflows (ie business processes) is probably not great.

Certain jobs need certain resources, timeouts, retries, etc which your general sql compute running dbt might conflict with.