Issue #11449 has been updated by Michael Knox.
The need to allow user input customisation of a fact is a major discussion for the mountpoint fact (#2847). In that case the debate is about how to provide customisations for a default 'ignore' array. If the customisations are applied via a local config then I need to ensure that they are in place and up-to date before the Puppet run, thus creating a chicken & egg problem. I would prefer to be able to specify customisations through the Puppet DSL as this keeps everything in a central place. That said, local config files is probably the easiest way to ensure that customisations are available to most/all other consumers of facter data such as MCollective etc. ---------------------------------------- Feature #11449: Facter should have a configuration file https://projects.puppetlabs.com/issues/11449 Author: Adrien Thebo Status: Needs Decision Priority: Normal Assignee: Category: Target version: Keywords: Branch: Affected Facter version: There are increasing cases where facts need more variability or customizability than what is currently possible. Adding a configuration file that would allow people to make site-specific customizations, or enable/disable facts, or other such modifications would make facter more powerful and flexible. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
