This is basically why I ended up writing Runnable Plans, over at https://github.com/vatine/runnable-plans/ https://github.com/vatine/runnable-plans/, the main d

This is basically why I ended up writing Runnable Plans, over at https://github.com/vatine/runnable-plans/ https://github.com/vatine/runnable-plans/, the main differences are "you define the plan in YAML" (yeah, horrible, but better than hand-chasing a parser, that MAY come at a later date) instead of "in the script", "the plan has no inherent order" (to allow for future parallel execution), "saves success/failure to allow for later restart", and "can generate a GraphViz graph of the plan dependency ordering". But, whatever works, works. Start somewhere, get it into a script, plan, whatever. Then, it is easier to identify steps that can be turned to entirely machine-operated.