Issue #21792 has been updated by Zachary Stern. Keywords set to customer
---------------------------------------- Feature #21792: Facter needs the ability to better control its search paths https://projects.puppetlabs.com/issues/21792#change-94851 * Author: Andrew Parker * Status: Accepted * Priority: Normal * Assignee: * Category: * Target version: * Keywords: customer * Branch: * Affected Facter version: ---------------------------------------- Right now the only way to programmatically control the search paths in Facter is to use `Facter.search(path1, path2, ...)`. This only allows adding of paths and not removal or setting absolutely the paths. When Puppet uses Facter it needs to make sure that Facter will also search a known set of paths (the factpath and lib dirs in the modulepath) that may change over time. So in order for puppet to properly control facter it needs to be able to fully control (short of the base set of paths Facter always uses) the search paths. Ideally Facter would become a class that can be instantiated and is configured with where to find facts: <pre> facter = Facter.new(module_paths.concat(fact_paths)) facter.each do |fact| puts "#{fact.name} => #{fact.value}" end </pre> This would allow a large amount of control over Facter that we currently don't have. Another way of doing this that would be acceptable is to provide a `#search=(list)` method: <pre> Facter.search = module_paths.concat(fact_paths) </pre> -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
