For the record, I run into this problem all the time. I ended up effectively "inverting" the inheritance hierarchy of my nodes so that instead of inheriting, they just duplicate the same includes with a different set of "global" variables preceding them. It works, but it's clearly suboptimal.
On Mon, Nov 17, 2008 at 12:48 PM, Luke Kanies <[EMAIL PROTECTED]> wrote: >> Any suggestion for a more elegant solution would be appreciated. > > An external node solution would work much better. IIRC, the external nodes feature doesn't support the same capabilities. For example, I don't believe an external nodes script can use "define". So if you have defines with attributes that vary from node to node, I don't know how you'd do it with external nodes in a way that wasn't more trouble than it's worth. An external node system that supported all the constructs the puppet language supports would be great. I'd also like a pony. :) But in the meantime, even something as basic as allowing external scripts to return puppet code that just gets parsed and 'eval'-ed, though admittedly ghetto, would make my life a lot easier. deepak --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
