Re: Newbie questions

Hello everyone,

Thank you for the clarifications, I think I also understand CFEngine a
bit better.

 > Installing and bootstrapping to a hub and then figuring things out
 > is totally possible. That's I think what most people do. By default
 > the MPF doesn't really do much of anything.
Yeah well, I find it quite puzzling that CFEngine doesn't have this kind
of behavior out of the box, I feel like everything rests on this brittle
assumption that CFEngine is installed in /var/cfengine .

So from what I understand - I will have to modify the default MPF update
scripts, so that, on the agent, it somehow "calculates" the paths?

 > I am not sure what you mean by "is the file structure just coupled
 > together everywhere".
What I mean is that, with MPF by default, the installation path of
CFEngine needs to be the same in every agent.

 > I think it's important to remember that bundles are not functions
Yes, I think what I really needed to see are the custom policies, that's
what I was looking for - a way to extend CFEngine.
For now I've gone with a more pragmatic approach of using relevant tools
that handle idempotency, like docker-compose and Terraform, we'll see
how it goes.

 > I meant to ask but apparently forgot, when you say:
 >> I've seen that bundles can modify variables and define class in
 >> the parent scope, but that seems quite horrible.
 > Can you point me to where you see this?
I think this is it:
https://docs.cfengine.com/docs/3.26/reference-promise-types-methods.html#usebundle

I've said it's "quite horrible" - that might be an exaggeration, it's
just weird coming from a programming background.

Regards,
Jakub Wardyn

-- 
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 visit https://groups.google.com/d/msgid/help-cfengine/15f4ed6c-1bb0-4210-bb6a-d6a4dce13de6%40gmail.com.