On Thursday, January 24, 2013 6:01:46 PM UTC-6, Gonzalo wrote:
>
> Hi All,
>
> I have finally switched to using hiera (worthy goal!) and I am looking for
> a flexible way to manage the 'exclude' line in /etc/yum.conf.
>
> I want to be able to specify from different classes RPMs to be excluded in
> /etc/yum.conf, then build the exclude line from all those classes that set
> an exclude.
>
> In my hiera hierarchy, I use %{calling_module}, but I actually modify the
> yum.conf exclude line from a "yum" module so of course setting yum_excludes
> in various classes and calling hiera_array('yum_excludes') is not going to
> work as the %{calling_module} will be "yum".
>
> Any ideas?
>
>
Puppet's architecture does not lend itself to constructing values
iteratively, and what Hiera brings to the table in that area does not apply
to the scenario you describe. There are a couple of ways you might be able
to work around Puppet's constraints there, but before you go that way I
would suggest that you consider alternative strategies.
Let's start with why you want to add package exclusions to yum.conf via
multiple modules. I have some ideas of why you might be trying to
implement such a design, but I'd prefer to avoid guessing.
John
--
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.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
