On Nov 18, 6:20 pm, Gonzalo Servat <[email protected]> wrote: > On Sat, Nov 19, 2011 at 12:58 AM, jcbollinger > <[email protected]>wrote: > > > [..snip..] > > You have a great use case here for external data: instead of using a > > > node variable to communicate the machine's purpose, you could instead > > have class motd look it up via extlookup() or hiera. > > Thanks for replying John. I hadn't looked into extlookup() until you > mentioned this. It's just what I need! I also have a custom facter variable > that defines which data centre the server is in, which fits in nicely with > extlookup() to look into a dc-specific CSV file.
Great, I'm glad to hear it. > I'm not using ENC as I do call a few defines from node definitions, and I > don't think there is a way of calling defines from a YAML node definition? You are correct. External node classifiers cannot declare individual resources, including defined type instances. You would have to wrap yours in classes to use an ENC. I'm sure it would be possible, but it might be more work than you want to undertake right now. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
