On Sat, Jan 26, 2013 at 1:38 AM, jcbollinger <john.bollin...@stjude.org>wrote:
> > 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. > Hi John, Thanks for your reply. To be honest, I think in this particular case it's more about trying to work out how to solve this type of problem, perhaps not necessarily useful with this exclude line issue. One hypothetical example might be constructing a "users=" line for some config file and I want to set users from various modules to construct the line. For this exclude line question, I have a class that many nodes "include" and they all need to exclude one particular RPM to ensure a "yum update" never upgrades it. These same servers "include" another class, which also have a package to be excluded. Do you have any ideas on how to solve this type of problem? - Gonzalo -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@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.
