On Wed, Jun 26, 2013 at 6:57 AM, Erik Dalén <[email protected]>wrote:
>
> A big +1 from me for having the feature. I've needed it a couple of times,
> and the easiest workaround when not having it is simply data duplication,
> which is really bad.
> In some cases I've worked around that data duplication using more code,
> but usually a bunch of class inheritances in puppet, which IMO is even more
> magical and non obvious.
>
> Also I think this is a much better thing than the Puppet scope variable
> interpolation, for example I want other systems than puppet to be able to
> query the hiera data which this allows but the %{} interpolation doesn't.
>
> As to the exact syntax I'm quite indifferent, but I would like the hiera
> CLI or other things to be able to lookup values, which Henrik's
> %{lookup(key)} proposal might have a hard time doing.
>
This is closest to my opinion. I am worried it's going to lead to more and
more nested nightmares in production where you have to leap around all over
the place to find out what ultimately feeds into Puppet (which is a
probably today) but I've also done awful things in manifests to avoid
duplication, and like Erik I've ended up with either a hodge-podge of
functions or a bunch of class inheritance.
While I'm not a super fan of the idea I would prefer to keep this
functionality in Hiera so that the manifests stay simple.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-dev.
For more options, visit https://groups.google.com/groups/opt_out.
