Re: Package Module Materialization
"'Nick Anderson' via help-cfengine" <[email protected]>
| Newsgroups | gmane.comp.sysutils.cfengine.general |
|---|---|
| Message-ID | <[email protected]> |
\( ﾟ◡ﾟ)/ https://cfengine.com/blog/2022/example-custom-policy-update-cfbs-module/ On Sunday, January 30, 2022 at 10:42:25 AM UTC-6 Bryan Burke wrote: > Awesome, thanks for all the information! Everything is currently working > for me so there's no rush for me to change it, but I plan to move more > hosts to this in the near future and may revisit. I'll reference this > information, and if I have any suggestions, etc. I'll submit a PR. > > Cheers, > Bryan > > On Tue, Dec 14, 2021 at 7:49 AM Nick Anderson <[email protected]> > wrote: > >> Bryan Burke <[email protected]> writes: >> >> Thank you, Nick! Yes, this appears to be what I was looking for; not sure >> why I couldn't find it before. >> >> I added nodes for modules to the rendered MPF docs >> <https://docs.cfengine.com/docs/3.18/reference-masterfiles-policy-framework-modules.html>. >> >> >> If you would like to contribute to the modules docs please make PRs here >> <https://github.com/cfengine/documentation/blob/master/reference/masterfiles-policy-framework/modules.markdown>. >> >> >> As for the second question: "it looks like the update mechanism is a lot >> more flexible these days, and I'm wondering if I really need to do what I'm >> doing anymore. Is that possible, and are there any pointers to doing so?" >> >> looking at that file, I get some hints on how to hook in my own update >> mechanism. Seems that if it's defined, it is used completely in place of >> the normal update mechanism? Still not sure how well the whole thing would >> work without a policy_hub defined, but I can maybe try it out sometime >> soon. Any docs that describe this, or should I just be looking at the >> masterfiles source? >> >> Yes, we have really tried to make it easy to hook into the MPF and change >> it's behavior without having to resort to modifying the vendored policy. >> Instrumenting a custom update policy is pretty straight forward, if you >> have some suggestions for where docs for this need to be improved feel free >> to open a pr or at least share a link to where in the docs and then some >> suggested verbiage so someone else can get it added. >> >> You can define your own update mechanism by: >> >> - Adding your custom update policy to update inputs >> - From the root of the MPF docs in the Reference manual: Append to >> inputs used by update policy >> <https://docs.cfengine.com/docs/3.18/reference-masterfiles-policy-framework.html#append-to-inputs-used-by-update-policy> >> - Setting the name of the bundle to use for policy update >> - From the root of the MPF docs in the Reference manual: Specify >> the agent bundle used for policy update >> <https://docs.cfengine.com/docs/3.18/reference-masterfiles-policy-framework.html#specify-the-agent-bundle-used-for-policy-update> >> >> That should be all you need to do. >> > -- >> Nick Anderson | Doer of Things | (+1) 785-550-1767 <(785)%20550-1767> | >> https://northern.tech >> > -- 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/5981e1dc-75d4-4b53-8b6e-7514c4a13238n%40googlegroups.com.