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 functionality is needed; especially for quick one-off things. So he's basically started creating one class containing 'create_resource' declarations for the standard Puppet resource types (file, user, group, exec, etc.). Then he just adds all of the appropriate parameters in hashes in Hiera. He's convinced this is the right way to do it since he hasn't yet ran into a scenario where this doesn't work easily. I told him if it was the right way then all the smart people working with and developing Puppet would have put it out as the best practice. However, I can't seem to come up with a really great scenario that will convince him. Can anyone share thoughts on scenarios where this patter will blow up [hard]? Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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/puppet-users/c46b1e54-f3c1-4429-b270-68189e6937f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
