Re: updates to update mechanisms and cf_promises_validated

"'Nick Anderson' via help-cfengine" <[email protected]> Thu, 20 May 2021 12:30:20 -0500

Newsgroups	gmane.comp.sysutils.cfengine.general
Message-ID	<[email protected]>

Hi Valentin,

By default the update policy only updates inputs to clients when
`validated_updates_ready' is defined. By default, this happens when
`cf_promises_validated' in inputs is repaired.

<https://github.com/cfengine/masterfiles/blob/2f0ba2892d3ad7eea7284ba6dfedcba5171612d0/cfe_internal/update/update_policy.cf#L235-L245>

`cf-agent' updates `$(sys.masterdir)/cf_promises_validated' when it
validates new policy in inputs. When this happens on the hub, then
remote agents will see that a policy update is available. However,
cf-agent doesn't currently consider any change to inputs a change to
policy. Instead of relying on this automatic realization of new policy,
it's more reliable to explicitly tag the policy when you change it
(`cf-promises --tag-release'). The masterfiles-stage tooling to
automatically deploy from from a version control repository does this,
you might consider using that.

- <https://github.com/cfengine/core/tree/master/contrib/masterfiles-stage>
- <https://docs.cfengine.com/docs/master/enterprise-cfengine-guide-hub_administration-policy-deployment.html>
- <https://www.youtube.com/watch?v=nsx5LT8iFjA>

--
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/87tumxia8j.fsf%40northern.tech.

--
Nick Anderson | Doer of Things | (+1) 785-550-1767 | https://northern.tech