> On 1 Mar 2016, at 19:52, Eric Sorenson <[email protected]> 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.
Some individual facts might benefit from configuration. - never consider docker*,and,others for ipaddress fact - ec2 facts IP address to hit - default gateway device - override some paths to required binaries Etc, tons of these. So some way that we all agree on to ingest config on a per fact basis > > --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. -- 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/3C1D9D77-61CF-49A1-90AB-E7277BB9B636%40devco.net. For more options, visit https://groups.google.com/d/optout.
