diff options
author | Sean Whitton <spwhitton@spwhitton.name> | 2021-03-13 14:01:38 -0700 |
---|---|---|
committer | Sean Whitton <spwhitton@spwhitton.name> | 2021-03-15 17:18:39 -0700 |
commit | db650186699ec82de2cfc9c2cbed1816b231cfec (patch) | |
tree | 0a93e8f3c3fce0bf0939c2431d72be44bcc4780b /doc | |
parent | 79b0da1845e75f15fffe73b137cc643c469d1c56 (diff) | |
download | consfigurator-db650186699ec82de2cfc9c2cbed1816b231cfec.tar.gz |
attempt to implement revised propspecs spec
Signed-off-by: Sean Whitton <spwhitton@spwhitton.name>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/ideas.rst | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/ideas.rst b/doc/ideas.rst index c18b82d..c2996fa 100644 --- a/doc/ideas.rst +++ b/doc/ideas.rst @@ -56,12 +56,14 @@ Core useful surrounding a set of DEPLOYS applications, to concurrently deploy a number of hosts. -- A combinator which makes a list of properties unordered, i.e., later ones - don't depend on earlier ones. Then when applying, if we get FAILED-CHANGE, - we can just move on to the next property. The implicit dependency - relationships in the absence of this combinator is a good default, as almost - every defproplist will want that. But we might want to make this combinator - implicit in DEFHOST. +- It might be useful to have a restart for the case where an attempt is made + to apply a list of properties containing some ``:LISP`` properties with a + POSIX-type connection which applies properties up to but not including the + first ``:LISP`` property in the sequence, to get as much work as possible + done without violating any dependency relationships (``SEQPROPS`` already + handles wanting to apply all of the ``:POSIX`` properties in the sequence). + But maybe this is unnecessarily complex -- wouldn't it be better to just + fail and fix your deployment definitions? Project & packaging ------------------- |