[
https://issues.apache.org/jira/browse/AIRFLOW-6925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamil Bregula updated AIRFLOW-6925:
-----------------------------------
Description:
We currently have one [experimental
API|https://airflow.readthedocs.io/en/latest/rest-api-ref.html], 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 HATEOS 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|https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-13%3A+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.
was:This is epic issues used for tracking to track work on Apache Airflow
described in AIP-XXXXX
> AIP-32: Airflow REST API
> -------------------------
>
> Key: AIRFLOW-6925
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6925
> Project: Apache Airflow
> Issue Type: Epic
> Components: api
> Affects Versions: 2.0.0
> Reporter: Kamil Bregula
> Assignee: Kamil Bregula
> Priority: Major
>
> We currently have one [experimental
> API|https://airflow.readthedocs.io/en/latest/rest-api-ref.html], 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 HATEOS 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|https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-13%3A+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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
