Issue #11449 has been updated by Daniel Pittman.
Ken Barber wrote: > I'm not sure - but this might be needed for 1.7.x, so lets place it there for > now (better then leaving the target blank). FWIW, I wouldn't expect to see a solution to this ticket until it was part of a branch that added a consumer of that configuration file; since it isn't currently related to any tickets that need configuration to be added, I would have said "unscheduled" was the best state for this. (Specifically, "unscheduled, waiting for a use case before we add the code") ---------------------------------------- Feature #11449: Facter should have a configuration file https://projects.puppetlabs.com/issues/11449 Author: Adrien Thebo Status: Accepted Priority: Normal Assignee: Category: Target version: 1.7.x 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.
