I'm doing a refactor of my puppet code with the profiles+roles design
pattern. I'm encountering what should be a simple problem, but I'm having
trouble finding an answer.
With roles/profiles, you instantiate classes using 'include' and fetch the
parameter values from hiera. Then, for each nod
Hi Mike,
I've not done that, but from glancing at the documentation on the Module's
Forge page, there don't seem to be any requirements around that besides
running a PE agent on that node.
I don't know anything about how it hits those APIs on the F5 though.
I believe you can use "puppet resource
Hi,
This is mostly a "rethink what you are doing" reply, based on my experience
of starting with our business logic of an estate almost entirely coded in
Hiera, and now moving towards a role/profile design. If it doesn't fit,
feel free to tell ignore, I've answered your question at the end :-
Jim,
The puppet server 2.5.0 release had a few changes with respect to
bootstrap.cfg (there are details about it here:
https://docs.puppet.com/puppetserver/2.5/bootstrap_upgrade_notes.html). In
your case it looks like you had modified /etc/sysconfig/puppetserver to
change the heap size, so yum was
