Closed davemackintosh closed 9 years ago
Yeah, not sure how to handle this, maybe prepend the command.
I was thinking the same, maybe we need to think about a hook system rather than a hard coded set of values or the ability to have arrays of actions to complete per step.
Maybe we need a pre-[phase], post-[phase] events, really all of the phases should be events.
It would be minimal work to set up a loop around those keys? Would need to check their type first so to remain backwards compatible but doesn't seem like a lot of work to me.
Actually I think they already are events, so yeah, would be pretty trivial.
Do you want to do that or should I fork and do that shortly?
@davemackintosh if you have time, a PR would be great, I'm crunching some client work.
No worries, I am as well but I'll get to this once I'm done :)
I will get round to this today or tomorrow, lots of work to do with deadlines!
I do need to rebase my branch and fix conflicts, but note that if #11 moves forward then this issue will be resolved as a side-effect.
Closing in favor of #11
Setting the phase to build image on to
prepare
causes the tar to not happen which breaks everything. Introduced in last PR #8.