curious if anyone has experimented with dbt defer with dagster? locally when running the dbt cli we have a wrapper script that runs something like the following:

dbt ${run/build/test} --project-dir ... --profiles-dir ... --defer --state target/prod --target local --target-path target/local  --select ...

This essentially materializes all the selected assets, and uses the local version of deps when available, else uses the prod version. It would nice to mimic this with dagster locally, especially when working with models that rely on an upstream dbt asset. In dagster world it seems like we'd need to have

--defer

and

--state

added as options to

dbt_cli_resource

in order to accomplish something similar when running locally? Are there other options? Would adding those be something feasible?

Pretty sure the dbt CLI resource is already capable of passing arbitrary arguments to commands…

oh wonderful it works, thanks! couldn't find that in the docs but see it in the implementation now

I think this would fit great into a branching IO manager for DBT