----- Original Message -----
> From: "jcbollinger" <john.bollin...@stjude.org>
> To: puppet-users@googlegroups.com
> Sent: Monday, October 15, 2012 3:35:30 PM
> Subject: [Puppet Users] Re: Puppet 3.0.0 and Hiera
>
>
>
> 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?
>
>
the param classes integration with hiera in puppet 3 does make it
worth taking another look at param classes:
The code:
class x($y="hello") {
notify{$y: }
}
include x
include x
actually works fine, note this is basically your old school puppet
syntax, multiple calls to include etc, but with hiera integration
for the variable key "x::y".
this deals with the dynamic scoping problem, deals with most of the
things I hate(d) about param classes and gives me magical abilities
to do overrides where and how I need them.
You can still if u wish use the new param classes style of including,
ENC etc can all supply data just like always.
from a code share perspective this is a big win, simply using param
classes means your module is forwards and backwards compatible with
hiera or without hiera.
--
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.
