Just a clarification: “reverse” flow is what I usually call “dependency based
flow” when we specify dependencies between tasks rather then direct transitions
(do this then on success do that).
> * Put it off till the engine refactoring, factor the requirement of
> supporting two modes into the
https://review.openstack.org/#/c/100390/
Angus asked:
>Why do we even need "start: "?
>Can't we parse the workbook and figure out what to run? Tasks at the bottom of
>the tree have no "on-{fail,success}" and then
>follow upwards until you find a task that is not referenced by anything.
Yes we
