I believe that wouldn't be equivalent, as the use case here is to keep poking until a script/bash command returns 0.
To clarify, I needed this because I wanted to wait for a certain condition to become True, but checking that condition meant SSH'ing into a machine and looking for the presence of a few files, with some logic in between. Cheers, On 28 July 2017 at 17:44, Stefano Baghino <stefano.bagh...@teralytics.ch> wrote: > Couldn't this be achieved by simply making the script that needs the sensor > a dependency of the one that emits the return code? > > On Fri, Jul 28, 2017 at 4:12 PM, Diogo Franco <diogoalexfra...@gmail.com> > wrote: > > > Hi, > > > > I was looking for a sensor that allowed me to customize the sensing > logic. > > I couldn't find any way of doing this and wrote a BashSensor, which > returns > > True or False based on a command/script's return code. The implementation > > is similar to the BashOperator, and it seems to me that it would fit > pretty > > naturally within airflow. > > > > Is there another way to achieve this that I don't know about? If you > think > > it is worthwhile, I'm happy to work on some tests and a PR. > > > > Thank you! > > > > > > -- > Stefano Baghino | TERALYTICS > *software engineer* > > Teralytics AG | Zollstrasse 62 | 8005 Zurich | Switzerland > phone: +41 43 508 24 57 > email: stefano.bagh...@teralytics.ch > www.teralytics.net > > Company registration number: CH-020.3.037.709-7 | Trade register Canton > Zurich > Board of directors: Georg Polzer, Luciano Franceschina, Mark Schmitz, Yann > de Vries > > This e-mail message contains confidential information which is for the sole > attention and use of the intended recipient. Please notify us at once if > you think that it may not be intended for you and delete it immediately. >
