I don't think you understood my question Scott. In any case, I'm avoiding external nodes because you lose all ability to version control.
I found the solution anyway. It's to include the client node further up the node hierarchy, since all nodes will have the client, and then further down the node hierarchy include the server. Then, make the server inherit from the client, and override those resources in the server that are defined in the client. Seems to work nicely (so far). Doug. On Sun, Dec 13, 2009 at 9:00 PM, Scott Smith <sc...@ohlol.net> wrote: > Douglas Garstang wrote: >> What's the best approach for this? I could combine both the client and >> server into one module and simple use case statements to serve out >> files based on their hostname, but that seems ugly. Is there a better >> idea? Can I "UN" include a class? >> > > If you use external node lookup, you can specify that one node includes > syslog_ng::server and the > rest include syslog_ng::client. > > http://reductivelabs.com/trac/puppet/wiki/ExternalNodes > > -scott > > -- > > 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. > > > -- Regards, Douglas Garstang http://www.linkedin.com/in/garstang Email: doug.garst...@gmail.com Cell: +1-805-340-5627 -- 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.
