Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Sun, 27 Nov 2016 19:14:58 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.13002948.1473174661000.373756.1480274098359@Atlassian.JIRA>
In-Reply-To: <JIRA.13002948.1473174661000@Atlassian.JIRA>
References: <JIRA.13002948.1473174661000@Atlassian.JIRA> <JIRA.13002948.1473174661777@arcas>
Subject: [jira] [Commented] (AIRFLOW-489) Add API framework
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 27 Nov 2016 19:15:55 -0000


    [ https://issues.apache.org/jira/browse/AIRFLOW-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700170#comment-15700170 ] 

ASF subversion and git services commented on AIRFLOW-489:
---------------------------------------------------------

Commit d5ac6bd9d0257683d8b2d0b200a513b2f43ce5dc in incubator-airflow's branch refs/heads/master from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=d5ac6bd ]

[AIRFLOW-489] Add API Framework

This implements a framework for API calls to Airflow. Currently
all access is done by cli or web ui. Especially in the context
of the cli this raises security concerns which can be alleviated
with a secured API call over the wire.

Secondly integration with other systems is a bit harder if you have
to call a cli. For public facing endpoints JSON is used.

As an example the trigger_dag functionality is now made into a
API call.

Backwards compat is retained by switching to a LocalClient.


> Add API framework
> -----------------
>
>                 Key: AIRFLOW-489
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-489
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Bolke de Bruin
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)