kyprifog edited a comment on issue #9937: URL: https://github.com/apache/airflow/issues/9937#issuecomment-663092349
@potiuk I guess my point of reference here is the existing POST /dag_runs/ endpoint. That seems to set a prescedent for being able to create dag runs using the api. So why wouldn't you also have an endpoint for posting Dags as well? Also if not a rest api endpoint, this work seems like its 80% of the way to developing a concept of an external airflow registry and directionally consistent with that idea: https://airflow.apache.org/docs/stable/dag-serialization.html If you _were_ to build a sidecar I would think it would be this rather than something thats just syncing files from one place to another. I'm actually a huge fan of kubernetes and use it in most of my work, but even I can see that requiring a side car service and deployment in kubernetes or even multiple services with docker-compose doesn't really logically follow from being able to interact with one of the main objects of focus through the api. Thats just adding required external complexity for something that seems like it should be pretty basic. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
