> On Mar 1, 2016, at 12:25 PM, Matthew Gaspar <gat...@gmail.com> wrote:
> 
> A config file for facter is intriguing to me.
> 
> Would this solely be used to change behaviors when running facter, or do you 
> see some potential for defining some facts within the config itself?

I think it'd be only settings/behavior - if there were fact values, those can 
go into facts.d as yaml/json/executables today.  (Is there some reason that 
doesn't work for you?)

> 
> Also, would you move facter specific configs into this facter.conf instead of 
> being managed from the puppet.conf file (ie: cfacter, factpath, 
> fact_terminus)?

Hm, some of these are more settings that puppet uses to interact with facter. 
factpath would certainly move. 


> The only problem I sometimes encounter, which may be a usage issue on my 
> part, is when creating custom facts sometimes it'd be nice to just run 
> `facter my_custom_fact` to get the output. If there would be some way to 
> register custom facts so that facter picks them up without having to run 
> puppet or run the ruby code the custom fact is in manually, that would be 
> interesting. If that already exists I haven't found how to do that.
> 

Well, today you can run 'facter -p' to get it to load facts from the pluginsync 
target directory. Or make these external facts (standalone programs rather than 
ruby plugins) and they will be loaded on regular facter runs. 

https://docs.puppetlabs.com/facter/3.1/custom_facts.html#external-facts

Does that make sense?

> Either way, I think a config where you can either specify which facts to 
> enable or disable would be useful.


Right on, thanks for the reply!

Eric Sorenson - eric.soren...@puppetlabs.com 
<mailto:eric.soren...@puppetlabs.com> - freenode #puppet: eric0
puppet platform // coffee // techno // bicycles

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/3F415861-1637-49C6-B3DE-ECF3BC8116A5%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to