I tend to take the stance that things in modules that AREN'T specific to your company (i.e. things that could help others - like names of packages on other OS platforms, config file paths, etc) should be kept in the Module and not locked up in Hiera data (that way, both people using and NOT using Hiera can benefit from them). I HAVE in the past put that data in Hiera, but have also find that it can bloat the hierarchy. I'm curious as to what others think, as this is my opinion and not necessarily 'best practice'.
On Fri, Dec 7, 2012 at 10:13 AM, R.I.Pienaar <r...@devco.net> wrote: > > feedback on a possible approach towards dealing with this problem in -- Gary Larizza Professional Services Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
