Thanks Nan. I supposed every one's environment is different. For the facts.d, how does that work exactly?
On Feb 16, 4:31 pm, Nan Liu <[email protected]> wrote: > On Thu, Feb 16, 2012 at 3:52 PM, Tony C <[email protected]> wrote: > > I see, but following this page does allow for that > > >http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/Fact... > > > I just tested it. So in my enterprise, i would much rather control the > > facts.yaml using a module of the above listed link and a puppet run, > > than allowing a cron job to do this. Also, the parameters defined in > > the ENC really help me carve out my infrastructure nicely for my > > puppet manifests, as well as the ability to run queries in mcollective > > using these parameters. A good examle would be a group in the > > Dashboard called PRODUCTION, with a parameter for site=LA > > I can see scenarios where I wouldn't want to dump the entire ENC > content since there's confidential settings though relevant for that > system, I don't want to make discoverable through mco inventory. > > Since you are using PE, another options you can take advantage of > facts.d directory, and write out custom facts in key=value format in > txt file under /etc/puppetlabs/facter/facts.d/ > > See the puppet_enterprise_installer.txt for example, and this will be > a fairly straightforward file resource using a template. > > Thanks, > > Nan -- 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.
