There are times auto-loading resources from hiera data makes sense, such as
mlocal users or sudoer.d snippets (though PLEASE use .each instead of
create-resources!). These resources should absolutely be resources you in
no way manage anywhere else. For sudoer.d, you might “include sudo;
As a trivial example maybe we suddenly found that we needed to add a
configuration file to a bunch of systems quickly. Because my coworker's
class includes a generic call to 'create_resources("file")' we can
arbitrarily add any file with any content by simply adding some data to
Hiera.
There appears to be contradiction here.
If “one-off” changes for “new functionality” are needed, why are the changes
going into a base/profile module ?
Would some more specific and detailed examples be possible ?
—
"Sometimes I think the surest sign that
Hi all;
I'm a Linux engineer who went through a typical growth period with Puppet
and finally landed on the Roles and Profiles pattern which generally works
well.
I have a coworker that started on after me and doesn't like this pattern
and having to update profiles or base modules when new
