We've got a few updates landing on melty rainbow flame Meltano Hub melty rainbow flame today that I wanted to take a minute to call attention to: 1. EDK based utility plugins have been taken out of preview 🚀! This means that the recommended way to install transformers and orchestrators is now to use the utility plugin type i.e.

meltano add utility dbt-<adapter>

vs the traditional way using the plugin types

transformer

or

orchestrator

. Nothing is changing around the support for those existing

transformer

and

orchestrator

plugins but we're moving towards recommending the utility versions for new users. See the EDK docs for details on why we're moving in that direction. The Hub got a bit of an update to reflect these changes ✨. 2. More docs 📄 related to working in the Singer ecosystem singer logo. We want this to be a place to memorialize some of the less well known tips and tricks of working in the Singer ecosystem for both new and more experienced community members, things like: best practices, common patterns, and tips for evaluating a tap and target. Let us know if you have any thoughts or suggestions!

In general I’m very happy using the dbt-redshift EDK utility but I have run into some issues and questions. Most recently, I had wanted to run

dbt ls

but couldn’t, from the

dbt-redshift

utility (

meltano invoke dbt-redshift:ls

throws an error about an unrecognized command). I figured out eventually that only specific dbt commands are made available in the utility, and that they’re defined in the hub repository, not in the dbt-ext repository. It’d be great to have a way to run arbitrary commands for the executable that an EDK utility is wrapping.

@Matt Menzenski you should be able to pass arbitrary commands to the underlying executable if you remove the colon like

meltano invoke dbt-redshift ls

whoa! that’s a great tip, thank you! just tested and that works great 🦜