Breaking off from https://meltano.slack.com/archives/C0699V48BPF/p1744098201148729 discussing dagster and meltano My project so far has the meltano project at the top level, with dagster as a meltano utility, then using

dagster_meltano

(which I want to move away from). If I swap to using

dagster-meltano-pipelines

it looks like I should invert my project structure, scaffold a dagster project at the top level, and then my

meltano

project needs to be below that? Does that sound right?

> If I swap to using

dagster-meltano-pipelines

it looks like I should invert my project structure, scaffold a dagster project at the top level, and then my

meltano

project needs to be below that? Does that sound right? That's correct. There's an open issue to have the dagster plugin generate one asset per stream. I'm sure we could also generate "pipeline" assets and other Dagster definition (e.g. Schedules) from Meltano schedules and jobs, but there aren't any issue yet open for those.

Thanks Edgar. This blocked me from getting much further as the

dagster_meltano

library allows me to create multiple assets, one for each stream. I implement this as a multi-asset based on the

meltano run

op, and I do need to keep a yaml list of the tap's streams. These stream assets map 1:1 to my dbt sources. In a way it would be nicer to parse the dbt manifest for sources to avoid the double definition of streams, but that was way beyond me!

would you consider a PR for those?

Absolutely, PRs welcome!