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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/6b93869b-83b3-43dc-8784-bd2cf173e54c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
