On Aug 26, 2010, at 3:23 AM, puppetplayer wrote: > But the puppetclass attribute is also collected from the client and > all defined basenodes. > So i think there is a way to define attributes that are combined . Or > not?
I'm not sure what you're trying to say here. Are you saying class attributes are combined with those from the parent and not overridden by the most local values? In any case, I wasn't suggesting that class attributes in LDAP should work any differently, but classes in the manifests do. So don't use parent nodes at all, just classes. Then the classes will all be combined, or if you want, they can inherit from other classes. When inheriting from a class, I know you can override a value, but I imagine there's also a way to preserve that value and add to it (which sounds like what you're after). Although if each class was responsible for a list of "HostEntry" values, I would think simply calling those classes in sequence would do the trick and you could forget about inheritance. -- Rob McBroom <http://www.skurfer.com/> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
