On Thu, Sep 1, 2011 at 4:31 PM, Aaron Grewell <aaron.grew...@gmail.com>wrote:
> You can't. The whole purpose of facts is to allow Puppet to make decisions > based on client data. Variables=server, facts=client. > > Seriously??? I can edit mcollective's server.cfg file and change the factsource from facter to yaml, and then have puppet populate facts.yaml, which I think is actually easier and more manageable, but someone here has already gone and used custom facts, which means I have to use facter as the _only_ fact source. That's pretty lame. So, if I am stuck with this, how would I set a class of server for a particular node? Would I need to have puppet push out a text file containing the server class to the client, and then write a custom fact that reads the file from the client's OS? That seems like a much more complicated approach than setting 'server_class = web_server' in the node on the puppet master, and then having puppet put that in facts.yaml. Doug -- 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.
