On Friday, 19 July 2019 01:59:26 UTC+1, Lesley Kimmel wrote: > > Hi all; > > 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! >
Everyone else's replies touch on all the major points, so can't add too much more there. I do have an ageing blog post though, and it might be helpful... The post describes a contrived scenario based on a real-world problem; it starts with an engineering team working mostly out of Hiera YAML files, and then over time getting into a situation where that design pattern was causing too much pain, and thus the conversion to a role-profile pattern. All the internal technical secrets are obfuscated away behind this contrived scenario, but something very close to this happened to us - a medium sized company that's been using Puppet for 8+ years. The problem being solved is to do with creating networking on Linux servers, so it's a great deal more complicated than just adding a package to a machine. However if you can understand the concepts and the challenges faced, it might work as a real-world example for your Junior staff member... Maybe... 30% chance :-) The first half of the page is the scenario / blog post (which is the bit you want), the next is the docs for the example module itself describing our solution (which won't be useful to you): https://github.com/lukebigum/puppet-networking-example -- 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/73e43d92-bfec-4f67-a829-3d28953b12c9%40googlegroups.com.
