[
https://issues.apache.org/jira/browse/AIRFLOW-5860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Douglas Mendez updated AIRFLOW-5860:
------------------------------------
Description:
We are using experimental REST API for automating Airflow Dag, triggering Dags
from one of our microservices. It would be great for us to have within the API
response the dagrun_id to keep track of it with ease.
*Response example*
{code:java}
// code placeholder
{
'execution_date': execution_date,
'message': message,
'dagrun_id': 'dagrun_id
}
{code}
was:
We are using experimental REST API for automating Airflow, triggering Dags from
one of our microservices.
If the API could return the `dagrun_id` it would be great for us, we could save
it in our DB with data related, with this we could find the log for specific
DAgRun quickly.
*Response example*
{code:java}
// code placeholder
{
'execution_date': execution_date,
'message': message,
'dagrun_id': 'dagrun_id
}
{code}
> Add the field `dagrun_id` to the response of experimental API on trigger.
> -------------------------------------------------------------------------
>
> Key: AIRFLOW-5860
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5860
> Project: Apache Airflow
> Issue Type: Improvement
> Components: api, cli
> Affects Versions: 1.10.6
> Reporter: Douglas Mendez
> Priority: Major
>
> We are using experimental REST API for automating Airflow Dag, triggering
> Dags from one of our microservices. It would be great for us to have within
> the API response the dagrun_id to keep track of it with ease.
>
>
> *Response example*
>
> {code:java}
> // code placeholder
> {
> 'execution_date': execution_date,
> 'message': message,
> 'dagrun_id': 'dagrun_id
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
