Hi puppet users, We've got a puppet (0.24.8) implementation with two environments, called production and testing. We've also got a Puppet Dashboard (1.0) instance up and running, which is receiving and displaying reports from hosts in both of the environments.
We would like to start using the dashboard as an external node classification tool, so I've taken the example from the puppet-dashboard source tree and it's working up to a point. My query is this: Why doesn't the dashboard understand which environment applies to the host, and return that in the yaml output? Here's the sample external node definition from the puppet docs. http://docs.puppetlabs.com/guides/external_nodes.html#external_node_scripts_for_version_023_and_later > #!/bin/sh > # Super-simple external_node script for versions 0.23 and later > cat <<"END" > --- > classes: > - common > - puppet > - dns > - ntp > environment: production > parameters: > puppet_server: puppet.example.com > dns_server: ns.example.com > mail_server: mail.example.com > END > exit 0 And here's the default output from the external node tool. > - name: server.example.com > parameters: {} > > classes: [] > ...without the environment defined. At the moment, all of our testing environment clients are defined as such in their own puppet.conf files, but we wanted to remove this requirement by making it part of the external node definition. I know that I could use a parameter for it, because I'm already managing the puppet.conf file on the clients, but that seems a little convoluted. Is this something that is better handled another way, or is it on the roadmap for the puppet dashboard? many thanks, Ben -- -- 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.
