On Mon, May 31, 2010 at 9:17 PM, James Turnbull <ja...@puppetlabs.com>wrote:
> John Warburton wrote: > > > > This is nice. Can we go the whole hog and provide all configuration > > options as facts? Could have a unique name space of something like > > CONF_variable --> CONF_certname > > I though I logged a feature request for this a while ago but damned if I > can find it now - so feel free to log one. > > > For now, I'd like to use Nigel's code to bulk load these options, and it > > got me thinking that the configuration file location must be known by > > the client as well. How do I get it? > > It's much like Nigel's code and has some hard-coded options. If you > know where it is on your hosts you can use Nigel's code and iterate over > the options and output them as facts pretty easily. > The *only* reason I'm hard-coding the config file is so that when non-root users run 'facter' they get the same results. Otherwise I wouldn't bother. > > Regards > > James Turnbull > > -- > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- nigel -- 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.
