Phases and lifecycle

[Jonathan Woods]

Hi!  I wonder if someone could clarify a couple of things about Pallet's concept of phases.

I understand that :bootstrap, :settings and :configure have special significance and can be considered part of a Pallet operations lifecycle.  But from what I can tell at the moment it seems that phases outside these are merely arbitrary bundles of crates and operations.  Is there any native concept of a custom lifecycle (like [:bootstrap :configure :install-app-server :run-the-thing]) in which given a later phase, Pallet will automatically go through all earlier ones?  I realise it's possible to code that up, but just in case I'm missing something...

Separately, but relatedly, is there a Pallet-idiomatic way of storing on a node the phases through which it has been taken?  E.g. in pallet-state (/var/lib/pallet) a list of phases which had been applied.  Something like that would help in cases where there is a meaningful notion of 'ensure idempotently' for a phase.

Jon

[Hugo Duncan]

Both converge and lift can be passed a sequence of phases to execute.

The default phases can be specified as a sequence on the
`:default-phases` key of a server or group spec. The default-phases are
composed when using `:extends` on a server-spec.