I think skipping promises with unexpanded variables is a safe and simple
approach.
I have seen too many issues with configurations (and thus services)
being broken due to a variables not expanded for some reason. It is
better to leave old and working configurations in this case.
Unexpanded variables is a bug (either CFEngine or policy) and I don't
think we should proceed, but flag the given promise as not kept.
On 24/05/16 16:02, Nick Anderson wrote:
On 05/24/2016 08:22 AM, Dimitrios Apostolou wrote:
What would you guys think as the best behaviour?
In my opinion completely skipping promises with unexpanded variables
would make sense, because it seems that convergence was not achieved.
To me it makes sense to skip it until the final pass of convergence at
which time the literal value could be used. At least that makes sense to
me for a default behavior from the perspective of trying to do the
correct thing without any specific instruction. I also think it would
make sense to have the ability to indicate that a promise that contains
an unexpanded var is not actuated (to allow for easier avoidance of bad
behavior when variables don't get defined).
Maybe thats too magical.
--
Eystein
--
You received this message because you are subscribed to the Google Groups
"dev-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dev-cfengine/5745856C.5030804%40cfengine.com.
For more options, visit https://groups.google.com/d/optout.
