On Tue, 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'd rather not mix config with content. If we want a facts.txt or something, that's cool, but not configuration. > > 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)? > I would like to see the search path for custom facts set in here. (And get facts.d out of /etc, cause I feel bad about that). There might also be something an 'expensive facts' list that we only resolve once a day, or custom TTL settings, or something to improve the performance of gathering facts. I'm just spitballing here though. > 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. > > Either way, I think a config where you can either specify which facts to > enable or disable would be useful. > > > On Tuesday, March 1, 2016 at 11:52:12 AM UTC-7, Eric Sorenson wrote: >> >> I've been thinking about a config file for Facter, which has historically >> not been run-time configurable. >> >> The two problems in front of me that seem applicable are: >> >> * Sometimes, certain facts are just plain bad to collect and users would >> like to prevent them from even being resolved (see FACT-718, FACT-449, ). >> * Some facts are not inherently bad but _are_ expensive and/or change >> infrequently, so preventing them from being resolved every time would be >> beneficial (FACT-348) >> >> Are there other problems you're running into in this area that you'd like >> to see addressed with a "facter.conf"? I'd like to gather all the >> requirements and start up a little Puppet RFC based on them. >> >> --eric0 >> >> -- > 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/0f42fe6f-1f75-4aff-aa6a-77dd3e17235c%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-dev/0f42fe6f-1f75-4aff-aa6a-77dd3e17235c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAMto7L%2BcB%2BEE55AX8CZsiJwBM5_a66uJ8F1sxN6OEttKRrDZhg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
