GitHub user marcopistacchio created a discussion: Hop Web | Airflow HTTP operator
Hello, I am investigating production deployment options for Hop. I would like to deploy Hop Web with a project and environment on a remote server and enable user authentication through Tomcat. This will enable users to connect to, design, and execute their Hop pipelines on a remote server without needing the local Hop GUI. I would then like to orchestrate their pipelines via Airflow. I would like to use the HTTP Airflow operator to ping the remote Hop Web deployment to execute the Hop pipeline with a [native local pipeline engine](https://hop.apache.org/manual/latest/pipeline/pipeline-run-configurations/native-local-pipeline-engine.html) run configuration. Airflow is running in a separate remote instance. The reason I prefer this deployment pattern over Hop Run is that it should eliminate the need to rebuild a Docker image when users create new Hop pipelines. Is this a possible and/or recommended pattern? Any feedback about this design? Thanks in advance. GitHub link: https://github.com/apache/hop/discussions/6095 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
