[jira] [Resolved] (AIRFLOW-2015) Add an --interactive switch to `airflow run`

["Fokko Driesprong (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AIRFLOW-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fokko Driesprong resolved AIRFLOW-2015.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request #2957
[https://github.com/apache/incubator-airflow/pull/2957]

> Add an --interactive switch to `airflow run`
> --------------------------------------------
>
>                 Key: AIRFLOW-2015
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2015
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: cli
>            Reporter: Yati
>            Assignee: Yati
>            Priority: Major
>             Fix For: 2.0.0
>
>
> The command
> {code:java}
> $ airflow run dag_id task_id xdate
> {code}
> redirects all output to the configured logger. For development of dags and of airflow itself, it is helpful to be able to put breakpoints in code. Capturing standard output and error streams in this case hinders this use case. Unless there already is a way to work around this, I propose addition of an --interactive. Example:
> {noformat}
> (airflow) ys@dock:~/incubator-airflow$ airflow run --force --interactive --local leader a '2018-01-16T00:00:00Z'
> ---logging snipped---
> > /home/ys/incubator-airflow/airflow/bin/cli.py(329)_run()
> -> if args.local:
> (Pdb)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)