luiztauffer opened a new issue, #24537: URL: https://github.com/apache/airflow/issues/24537
### Description Given that all DAGs are serialized in the database ([reference](https://airflow.apache.org/docs/apache-airflow/stable/dag-serialization.html)), it feels like a POST request in the [Airflow REST API](https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html) for creating DAGs would be a very useful improvement! It could accept already serialized dags, for example. Is this something that might be considered for an upcoming version? Thanks for all the great work, I’ve been loving working with Airflow! ### Use case/motivation My context: I’m working on a project where I start with JSON files defining newly created DAGs, and then I see myself having to turn those into Python files (I use Jinja2 templates for that) and having to upload these newly created .py files to a storage somewhere, where a running instance of Airflow can read the new DAGs. The above approach works, but certainly things could be better. The necessity of actual python files stored somewhere unnecessarily increases the complexity of each deployment. I would also appreciate other ideas to possibly circumvent this limitation. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
