Hello, I just created "AIP-32 - Airflow REST API" proposal and would love community feedback and comments. https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-32%3A+Airflow+REST+API I would love to know what is your expectation from the API.
We currently have one experimental API, but despite its existence for 2 years, it has not reached a stable level. There are many critical aspects to this implementation including no defined schema, very narrow range of functions, unsafe default configuration, no HATEOAS, and many others. In the past, Drewstone began work on REST API based on OpenAPI. It's described by AIP-13: OpenAPI 3 based API definition. However, it was not completed due to the lack of interest from the author and the Kerberos configuration problem (It was at a time when Breeze was still developing, so configuring all dependencies, including Kerberos, was a problem). It had a narrow range of features that are expected by users e.g. access to XCOM data and management for connection is missing, The Polidea and Google teams together with the community want to make another attempt based on our and community experience. Airflow deserves new stable solutions. Any comments and feedback/discussion in the AIP-32 document are welcome! Best regards, Kamil Breguła
