Re: Package Module Materialization

Thank you, Nick! Yes, this appears to be what I was looking for; not sure 
why I couldn't find it before.

As for the second question: 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?

Bryan

On Monday, November 29, 2021 at 9:21:18 PM UTC-8 [email protected] wrote:

> Is this the policy your looking for?
>
> https://github.com/cfengine/masterfiles/search?q=modules_presence
>
> On Sun, Nov 28, 2021, 8:22 PM Bryan Burke <[email protected]> wrote:
>
>> Greetings,
>> I'm updating a small installation I use from 3.12 => 3.18 (also CentOS 7 
>> => 8-stream), and I had some trouble with the package modules.
>>
>> They used to be packaged in masterfiles directly, but it looks like a few 
>> months ago, if my searching taught me anything, they were converted to 
>> mustache templates. Try as I might, however, I was unable to find where in 
>> the policies/updates the package modules got materialized. I'm assuming 
>> this is done for you somehow during bootstrap or update, but I couldn't 
>> figure it out.
>>
>> Mitigation: since it doesn't look like they actually have any 
>> interpolations in them, for now, I just copied the one I needed (yum) into 
>> place and distribute that, but I assume this will break at some point.
>>
>> Question: I want to make sure I'm materializing these correctly, so can 
>> someone advise me on how to do that?
>>
>> Context: why am I trying to materialize them directly? Well, I've got a 
>> pretty custom setup in Google Cloud. Cloud Storage is my distribution 
>> method, with service account credentials for authentication (more below, if 
>> you're interested). So, I've got a completely custom 
>> update.cf/bootstrap.cf that can authenticate and speak to Google Cloud 
>> Storage, do some basic setup, and install the latest version of my policy 
>> files.
>>
>> The policy files themselves are also from scratch (honestly I forgot why 
>> I did that at this point, but there was a reason, probably related to not 
>> having a policy server). That is, I define my own body common 
>> control/bundlesequence/inputs.
>>
>> Secondary 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?
>>
>> Additional context: I didn't want to run a policy server (costs $$$, and 
>> trying to make that accessible to different networks I manage, either with 
>> VPC peering or making the policy server public, were not desireable), so I 
>> made a custom distribution system.
>>
>> Thanks for any help you can provide! :)
>>
>> Bryan
>>
>> -- 
>> 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/1952fc38-63cb-42c4-8279-1a1ac940616en%40googlegroups.com 
>> <https://groups.google.com/d/msgid/help-cfengine/1952fc38-63cb-42c4-8279-1a1ac940616en%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/63c27345-7973-4807-ba0c-cccd032b38b7n%40googlegroups.com.