[jira] [Commented] (AIRFLOW-2528) Airflow cli does not allow disabled stdin

["Cameron Moberg (JIRA)" <ji...@apache.org>]

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

Cameron Moberg commented on AIRFLOW-2528:
-----------------------------------------

I believe this is fixed in master, from what I can tell.

Unable to reproduce when pulling from master.

> Airflow cli does not allow disabled stdin
> -----------------------------------------
>
>                 Key: AIRFLOW-2528
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2528
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: cli
>    Affects Versions: 1.9.0
>            Reporter: Brent Johnson
>            Assignee: Chao-Han Tsai
>            Priority: Major
>
> So basically, I am trying to automated regression testing by executing an airflow dag. I 
>  
> Using the cli I can successfully run the following command:
> {code:java}
> ./airflow run regression-testing regression-ingestion 2018-05-25{code}
> Unfortunately, I want to be triggering this against our staging instance in production on AWS.  
> I figured an easy way to do this would be to use [AWS System Manager|https://docs.aws.amazon.com/systems-manager/latest/userguide/run-command.html] unfortunately any airflow command I call returns:
> {code:java}
> the input device is not a TTY
> {code}
> I was able to recreate this running the following command locally by piping stdin to anywhere:
> {code:java}
> ./airflow run regression-testing regression-ingestion 2018-05-25 0>/dev/null{code}
> This is of course an extreme example but it feels like a bug for a cli to require stdin to be open.



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