On 01/03/16 19:52, 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
I would very much like to be able to type facts using the puppet type
system. While this could be done in other places, a Facter config would
be very useful to have server side when compiling as the compiler can
then validate against such a configuration without having to do the full
compilation with a full set of values.
This also opens up for the possibility to do real type inference. This
is not possible when facts are in essence untyped.
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
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/56D66026.9010501%40puppetlabs.com.
For more options, visit https://groups.google.com/d/optout.
