On Aug 5, 3:25 am, Thomas Rasmussen <rasmussen.tho...@gmail.com> wrote: > Hi > > Thanks for the reply, that works, but I'd like to keep my include of > the sudoers::config in my default node section, but if I do that, then > I don't have the $sudoenv variable available at that time. > > Is there any way of overriding a previously include of a class? I > tried to 'sudoers::config': sudoenv=> $sudoenv, stage => install; in > my server-defaults node definition, but puppet gave me a duplicate > error on include.
Not to my knowledge, no. If Vagn's suggestion for that works then I'll be quite surprised, and also very interested in hearing about it. > I'm running 2.6.4 on both server and client side. Another alternative is to set the variable by means other than the node declaration. The extlookup() function can be quite useful for this sort of thing. Be aware that it looks like you are going to *have* to do something along these lines in order to upgrade to 2.8.x (when that arrives). Yet another alternative might be to prune your node inheritance tree into two, one rooted at 'default' and a second rooted at 'server- default'. Each of those node declarations would define $sudoenv and include sudoers::config. If you want to adhere carefully to a DRY approach, then you can take everything common to the two node types, wrap it up in a class, and have each of the to default nodes include it. 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. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
