Hey all, I'm setting up Meltano UI as an ELT tool for a tap that I've written and another that isn't supported by stitch. Getting into the Orchestration bit, I was initially under the impression that Meltano provided a full drop in replacement of sorts for Stitch/Fivetran with the ELT functionality. Diving into it, I discovered that notifications are not something supported, and that orchestration "needs" to be done with airflow. This is a relatively simple setup, and was hoping that I'd be able to avoid airflow. Primary reason for using Meltano UI is predicated on not having to dig into Airflow and the painful UI, config, abstractions etc Wondering two things, first one relating to best practices 1. Is the Meltano UI viable for a simple ELT run scheduler? What shortcomings should I expect longer term? 2. Is there any discussion for a webhook for job status within the UI or even a webhook for the

meltano elt ..

command

Is the Meltano UI viable for a simple ELT run scheduler?

It’s not setup to run currently without using Airflow. I can open an issue on that though since that’s a reasonable expectation. However, we don’t want to go down the path of recreating the functionality of orchestrators, so I don’t think we’ll prioritize that. We should be able to make it super simple to get up and running though so you can avoid thinking too much about airflow/whatever orchestrator runs it under the hood.

Is there any discussion for a webhook for job status within the UI or even a webhook for the 

meltano elt ..

 command

We have https://gitlab.com/meltano/meltano/-/issues/2813 open which talks a bit about an API. Next year we’ll start refocusing on the UI since we’ve been so CLI focused for a while.

Thanks @taylor appreciate the responses. Agree that orchestration is something to enhance what exists, and hopefully can get to the same level with airflow as currently with the singer spec. Will follow along with that issue and think about how I can help more broadly. Cheers