REST API roadmap/plan?

[matthew <ma...@gmail.com>]

I've been poking around Jira and confluence but haven't seen any roadmap or
plans for the REST API.  Did I just miss it or has it stalled out?

I'm interested in working on it if it needs some help.

Thanks
-Matthew

Re: REST API roadmap/plan?

[matthew <ma...@gmail.com>]

I have to apologize.  After offering to help on the REST API, I haven't
been able to find any time to actually work on it.  Further, I don't know
when I will have time between now and the new year.

I definitely would like to help with this but I just don't know when that
will happen.

-Matthew

On Mon, Nov 5, 2018 at 12:10 PM Verdan Mahmood <ve...@gmail.com>
wrote:

> Hi Mathew,
> As Fokko mentioned, we don't have any roadmap for the REST API at
> the moment,
> but we can definitely start planning this out, gathering the list of APIs,
> review them together and making a roadmap.
> I'd be happy to help with this :)
>
> Few things:
> - I started out with a list of possible APIs a couple of months ago.
> https://issues.apache.org/jira/browse/AIRFLOW-2628
> - The experimental endpoints are functional views and scattered with no
> modular approach in place.
> We can definitely look for options like FAB REST API or Flask RESTful
> https://flask-appbuilder.readthedocs.io/en/latest/quickhowto.html#rest-api
> - Please consider using "www_rbac" for any new endpoint as we do have plans
> to deprecate
> the older "www" version of UI soon.
>
> Best,
> *Verdan Mahmood*
>
> On Mon, Nov 5, 2018 at 4:34 PM Driesprong, Fokko <fo...@driesprong.frl>
> wrote:
>
> > Thanks Matthew,
> >
> > We're working on getting the experimental API. This API should be used
> for
> > both the GUI and can be used for external systems to interface with
> Airflow
> > (triggering dags for example). Verdan was working on this, but for now,
> > this process is a bit stuck again. It turns out that data engineers
> aren't
> > really good at doing front end.
> > There isn't a full roadmap at the moment. There are some tickets, but
> > nothing with a full description:
> >
> >
> https://issues.apache.org/jira/browse/AIRFLOW-890?jql=project%20%3D%20AIRFLOW%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22REST%22
> >
> > Please feel free to pick this up and get rid of the logic from the GUI
> (web
> > interface), or extending the experimental API with sensible endpoints :-)
> >
> > If there are any questions, let me know.
> >
> > Cheers, Fokko
> >
> >
> >
> > Op wo 31 okt. 2018 om 21:00 schreef matthew <matthewp.donovan@gmail.com
> >:
> >
> > > I've been poking around Jira and confluence but haven't seen any
> roadmap
> > or
> > > plans for the REST API.  Did I just miss it or has it stalled out?
> > >
> > > I'm interested in working on it if it needs some help.
> > >
> > > Thanks
> > > -Matthew
> > >
> >
>

Re: REST API roadmap/plan?

[Verdan Mahmood <ve...@gmail.com>]

Hi Mathew,
As Fokko mentioned, we don't have any roadmap for the REST API at
the moment,
but we can definitely start planning this out, gathering the list of APIs,
review them together and making a roadmap.
I'd be happy to help with this :)

Few things:
- I started out with a list of possible APIs a couple of months ago.
https://issues.apache.org/jira/browse/AIRFLOW-2628
- The experimental endpoints are functional views and scattered with no
modular approach in place.
We can definitely look for options like FAB REST API or Flask RESTful
https://flask-appbuilder.readthedocs.io/en/latest/quickhowto.html#rest-api
- Please consider using "www_rbac" for any new endpoint as we do have plans
to deprecate
the older "www" version of UI soon.

Best,
*Verdan Mahmood*

On Mon, Nov 5, 2018 at 4:34 PM Driesprong, Fokko <fo...@driesprong.frl>
wrote:

> Thanks Matthew,
>
> We're working on getting the experimental API. This API should be used for
> both the GUI and can be used for external systems to interface with Airflow
> (triggering dags for example). Verdan was working on this, but for now,
> this process is a bit stuck again. It turns out that data engineers aren't
> really good at doing front end.
> There isn't a full roadmap at the moment. There are some tickets, but
> nothing with a full description:
>
> https://issues.apache.org/jira/browse/AIRFLOW-890?jql=project%20%3D%20AIRFLOW%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22REST%22
>
> Please feel free to pick this up and get rid of the logic from the GUI (web
> interface), or extending the experimental API with sensible endpoints :-)
>
> If there are any questions, let me know.
>
> Cheers, Fokko
>
>
>
> Op wo 31 okt. 2018 om 21:00 schreef matthew <ma...@gmail.com>:
>
> > I've been poking around Jira and confluence but haven't seen any roadmap
> or
> > plans for the REST API.  Did I just miss it or has it stalled out?
> >
> > I'm interested in working on it if it needs some help.
> >
> > Thanks
> > -Matthew
> >
>

Re: REST API roadmap/plan?

["Driesprong, Fokko" <fo...@driesprong.frl>]

Thanks Matthew,

We're working on getting the experimental API. This API should be used for
both the GUI and can be used for external systems to interface with Airflow
(triggering dags for example). Verdan was working on this, but for now,
this process is a bit stuck again. It turns out that data engineers aren't
really good at doing front end.
There isn't a full roadmap at the moment. There are some tickets, but
nothing with a full description:
https://issues.apache.org/jira/browse/AIRFLOW-890?jql=project%20%3D%20AIRFLOW%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22REST%22

Please feel free to pick this up and get rid of the logic from the GUI (web
interface), or extending the experimental API with sensible endpoints :-)

If there are any questions, let me know.

Cheers, Fokko



Op wo 31 okt. 2018 om 21:00 schreef matthew <ma...@gmail.com>:

> I've been poking around Jira and confluence but haven't seen any roadmap or
> plans for the REST API.  Did I just miss it or has it stalled out?
>
> I'm interested in working on it if it needs some help.
>
> Thanks
> -Matthew
>