Hi Björn, We also sometimes require manual validation, and though we haven't yet implemented this, I imagine you could store the approved/unapproved status of the job in a database, expose it via an API, and write an Airflow sensor that continuously polls that API until the status becomes "approved", at which point the DAG execution will continue.
Best, Alek Storm On Thu, Oct 4, 2018 at 10:05 AM Björn Pollex <bjoern.pol...@soundcloud.com.invalid> wrote: > Hi all, > > In some of our workflows we require a manual validation step, where some > generated data has to be reviewed by an authorised person before the > workflow can continue. We currently model this by using a custom dummy > operator that always fails. After the review, we manually mark it as > success and clear the downstream tasks. This works, but it would be nice to > have better representation of this in the UI. The customisation points for > plugins don’t seem to offer any way of customising UI for specific > operators. > > Does anyone else have similar use cases? How are you handling this? > > Cheers, > > Björn Pollex > >
