*EXPERIMENTS* Huh, it seems to return the DECLARED classes, not the defined ones, i.e. it can only see the modules and classes that are being applied to this particular node. OK, I could see an argument for that making sense. BUT: It also includes the names of any `node` constructs that match it (these are nodes defined in manifests, not from an ENC), and for some reason classes set via an ENC show up twice. I don't understand that. Also, there's one mystery class from Mars in there called "settings." What's THAT about.
On Feb 2, 5:50 pm, Nick Fagerlund <nick.fagerl...@puppetlabs.com> wrote: > On it. (Thanks for the example, Dan; that's pretty sweet.) > > Brian, what problem do you tend to see with the classes array? Does it > look like an order dependency? Is it just a crapshoot as to whether a > given class is in the list, or is there a method to it? > > On Feb 2, 5:18 pm, Brian Gallew <g...@gallew.org> wrote: > > > > > > > > > On Feb 2, 2011, at 4:57 PM, John Warburton wrote: > > > > I would love to see that > > > inhttp://docs.puppetlabs.com/guides/templating.htmlinthe "Access to > > > defined tags and classes" section. I have created a ticket for that > > > -https://projects.puppetlabs.com/issues/6124 > > > Sadly, there's also a great need to update that section to reflect the > > reality that the classes variable can never be relied upon to be in any way > > complete. -- 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.
