On Monday, October 15, 2012 7:35:30 AM UTC-7, jcbollinger wrote: > > > > On Friday, October 12, 2012 12:10:38 PM UTC-5, Ellison Marks wrote: >> >> Not to let this thread go to waste... >> >> Since I'm now trying to move away from the hiera functions themselves to >> the parameter style > > > > Why? The ability to achieve separation of data from code while avoiding > parametrized classes is one of the greatest advantages conferred by hiera. > Every parametrized-style class declaration (not definition) in your > manifests is a bug waiting to happen. And if you're not going to use such > declarations, then why do you want to spend effort on converting your > classes to make it possible? > > > John > > Er, perhaps I wasn't being clear, which is entirely possible.
I don't intend to use parametrized declarations(Right now I'm simply using hiera_include in the default node for everything and loving it). I do however, very much like the convenience of the new syntax. In addition, my use case for default values in the puppet backend that shipped with the class wasn't terribly complex, so simply including a default value in the class itself serves my needs well. In my case, the new features are simply a more convenient way of doing what i was already doing(sans the array and hash functionality). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/rLJp0Go7mw0J. 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.
