So I know from experience that meltano won't run the same pipeline multiple times concurrently, i.e.

meltano run tap-something some-mapper target-something

will complain if you run it and another instance is already running. But it appears that exclusivity check doesn't include transformers, i.e.

meltano run tap-something some-mapper target-something dbt-postgres:run

will start a second instance of dbt even if one is already running. Is that intentional? I expected the mutex checking to apply to the entire set of commands.

That seems like unintentional behavior - an issue would be appreciated. Putting it in a job context will help with terseness, but since behind the scenes it’s still calling meltano run I’d be surprised if it exhibitied different behavior

Thanks @taylor. I'll create a ticket on Monday.

Thank you!!