git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 答复: Airflow REST API proof of concept.


Personally I think we should keep the architecture as simple as possible
and use the same web server for REST and UI. As mentioned FAB (Flask App
Builder) manages authentication and RBAC, so we can have consistent access
rights in the UI and CLI.

Max

On Fri, May 11, 2018 at 5:42 AM Luke Diment <Luke.Diment@xxxxxxxxxxxxx>
wrote:

> Ok thanks that’s awesome we will have a look and check it out thanks...
>
> 🙂
>
> Sent from my iPhone
>
> > On 12/05/2018, at 12:38 AM, Driesprong, Fokko <fokko@xxxxxxxxxxxxxx>
> wrote:
> >
> > Hi Luke,
> >
> > This is the REST api for the new UI:
> >
> https://github.com/apache/incubator-airflow/blob/master/airflow/www_rbac/api/experimental/endpoints.py
> >
> > RBAC = Role Based Access Control, the fine grained security model based
> on
> > the fabmanager. Recently we've added some endpoints to it. In the end
> also
> > all the GUI ajax calls should go by this API, instead of calling the
> flask
> > endpoints directly.
> >
> > Cheers, Fokko
> >
> >
> >
> >
> >
> >
> > 2018-05-11 14:34 GMT+02:00 Luke Diment <Luke.Diment@xxxxxxxxxxxxx>:
> >
> >> Our build pipeline uses Jenkinsfile with Docker kubernetes and helm...we
> >> orchestrate deployment against our rest api and use junit to assert our
> >> results...fully programmatically against airflow...!
> >>
> >> Sent from my iPhone
> >>
> >>> On 12/05/2018, at 12:31 AM, Luke Diment <Luke.Diment@xxxxxxxxxxxxx>
> >> wrote:
> >>>
> >>> No it executes the backend airflow command line over HTTP giving
> >> developers room to freely interact with airflow programmatically...hence
> >> you can easily integration test your business logic...
> >>>
> >>> Sent from my iPhone
> >>>
> >>>> On 12/05/2018, at 12:27 AM, Song Liu <songliu@xxxxxxxxxxx> wrote:
> >>>>
> >>>> So that this Java REST API server is talking to the meta db directly ?
> >>>> ________________________________
> >>>> 发件人: Luke Diment <Luke.Diment@xxxxxxxxxxxxx>
> >>>> 发送时间: 2018年5月11日 12:22
> >>>> 收件人: dev@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >>>> 主题: Fwd: Airflow REST API proof of concept.
> >>>>
> >>>> FYI.
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>> Begin forwarded message:
> >>>>
> >>>> From: Luke Diment <Luke.Diment@xxxxxxxxxxxxx<mailto:
> >> Luke.Diment@xxxxxxxxxxxxx>>
> >>>> Date: 11 May 2018 at 1:02:43 PM NZST
> >>>> To: "dev-owner@xxxxxxxxxxxxxxxxxxxxxxxxxxxx<mailto:dev-owner@
> >> airflow.incubator.apache.org>" <dev-owner@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> <mailto:dev-owner@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>>
> >>>> Subject: Fw: Airflow REST API proof of concept.
> >>>>
> >>>>
> >>>> FYI.
> >>>>
> >>>> ________________________________
> >>>> From: Luke Diment
> >>>> Sent: Thursday, May 10, 2018 4:33 PM
> >>>> To: dev-subscribe@xxxxxxxxxxxxxxxxxxxxxxxxxxxx<mailto:de
> >> v-subscribe@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> >>>> Subject: Airflow REST API proof of concept.
> >>>>
> >>>>
> >>>> Hi Airflow contributors,
> >>>>
> >>>>
> >>>> I am a Java developer/full stack and lots of other stuff at Westpac
> >> Bank New Zealand.
> >>>>
> >>>>
> >>>> We currently use Airflow for task scheduling for a rather large
> >> integration project for financial risk assessment.
> >>>>
> >>>>
> >>>> During our development phase we started to understand that a REST API
> >> in front of Airflow would be a great idea.
> >>>>
> >>>>
> >>>> We realise that you guys have detailed there will a REST API at some
> >> stage.
> >>>>
> >>>>
> >>>> We have already built a proof of concept REST API implementation in
> >> Java (of course...;-))...
> >>>>
> >>>>
> >>>> We were wondering if your contributor group would find this helpful or
> >> if there would be any reason to continue such an API in Java.
> >>>>
> >>>>
> >>>> We look forward to your response.  We can share the code if needed...
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>>
> >>>> Luke Diment.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> The contents of this email and any attachments are confidential and
> may
> >> be legally privileged. If you are not the intended recipient please
> advise
> >> the sender immediately and delete the email and attachments. Any use,
> >> dissemination, reproduction or distribution of this email and any
> >> attachments by anyone other than the intended recipient is prohibited.
> >>>
> >>>
> >>>
> >>> The contents of this email and any attachments are confidential and may
> >> be legally privileged. If you are not the intended recipient please
> advise
> >> the sender immediately and delete the email and attachments. Any use,
> >> dissemination, reproduction or distribution of this email and any
> >> attachments by anyone other than the intended recipient is prohibited.
> >>
> >>
> >>
> >> The contents of this email and any attachments are confidential and may
> be
> >> legally privileged. If you are not the intended recipient please advise
> the
> >> sender immediately and delete the email and attachments. Any use,
> >> dissemination, reproduction or distribution of this email and any
> >> attachments by anyone other than the intended recipient is prohibited.
> >>
>
>
>
> The contents of this email and any attachments are confidential and may be
> legally privileged. If you are not the intended recipient please advise the
> sender immediately and delete the email and attachments. Any use,
> dissemination, reproduction or distribution of this email and any
> attachments by anyone other than the intended recipient is prohibited.
>