The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Any thoughts on how to best kick off a sensor when a dbt asset run completes? I'm loading assets from the manifest and would like to upload the new manifest to s3 after the models run

My initial thought is to write a sensor for the dbt op and materialize the s3 manifest asset in a run sensro

<@U01GTMVMGQH> <@U01J51Y6B9D> I actually found a resolution for the above. I ended up abandoning assets entirely in favor of ops/graphs. I find them to be much easier to use because they are documented well

I find that attempting to use assets leads to too many questions that I can't find answers to (either in the docs or in the slack support channel)

Thanks for flagging this, <@U03BJPRTZFV> - I'm actually focused on improving the asset docs now. If you don't mind sharing, were there other questions you had/have about assets that you couldn't resolve yourself? I'd like to make sure I account for them while I'm working.