Can dagster plus DBT core create something similar to dbt clous slim-ci feature? But E2E for all data data activities - not only what is happening inside DBT? Recently an example for a branching IO manager was added. Do you think you could add such a dagster-slim-ci branching example which includes DBT?

hi @geoHeil! I think code versioning can get you at least part of the way towards this. When we load your dbt assets (using

load_assets_from...

), we automatically generate a code version for each of the dbt models, based off of a hash of the sql. So in theory, each branch deployment should be able to know which of its definitions are net-new or net-different from the current version in the prod deployment (I don't think we currently compare code versions between branch deployments/prod but this is conceptually possible). This (in combination with the branching IO manager) would allow you to kick off a run of just the new/changed dbt models. Applying the same logic to code-versioned regular assets, I think this would essentially get to the state you're imagining. Seems like a bit of work on our side, but I think this is a pretty compelling use case

Such an example would be awesome