You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Anton Kumpan (Jira)" <ji...@apache.org> on 2019/11/08 03:10:00 UTC
[jira] [Updated] (AIRFLOW-5590) Add 'run_id' to trigger DAG run API
response as a field
[ https://issues.apache.org/jira/browse/AIRFLOW-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Kumpan updated AIRFLOW-5590:
----------------------------------
External issue URL: https://github.com/apache/airflow/pull/6256
> Add 'run_id' to trigger DAG run API response as a field
> -------------------------------------------------------
>
> Key: AIRFLOW-5590
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5590
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api
> Affects Versions: 1.10.5
> Reporter: Anton Kumpan
> Assignee: Anton Kumpan
> Priority: Major
>
> Idea is the same as in AIRFLOW-4482
> Currently API response looks like this:
> {code:json}
> {
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created <DagRun dag_id @ 2019-05-08 07:03:09+00:00: manual__2019-05-08T07:03:09+00:00, externally triggered: True>'
> }
> {code}
>
> It would be nice to add run_id as a separate field, so that response will look like:
> {code:json}
> {
> 'run_id': 'manual__2019-05-08T07:03:09+00:00',
> 'execution_date': '2019-05-08T07:03:09+00:00',
> 'message': 'Created <DagRun dag_id @ 2019-05-08 07:03:09+00:00: externally triggered: True>'
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)