Issue #2157 has been updated by Luke Kanies.

Subject changed from Scripted fact support (eg /etc/fact.d to External fact 
support in /etc/facter.d

Original description from Paul:

As a fact writer I want a mechanism to write facts in my favourite language and 
for facter to run them automatically so that I can easily write custom facts.

Given I have a configured directory for scripting facts
When a executable script that returns a key value pair is executed
Then the fact should be available in facter
----------------------------------------
Feature #2157: External fact support in /etc/facter.d
http://projects.puppetlabs.com/issues/2157

Author: Paul Nasrat
Status: Accepted
Priority: Normal
Assigned to: Paul Nasrat
Category: 
Target version: 2.0.0
Keywords: 
Branch: 


Facter should support non-ruby facts, preferably in /etc/facter.d.  It should 
support these facts being either executable, in which case the result is the 
value of the named fact, or in a data format such as yaml, in which case the 
data file is read in and interpreted as the fact value.

It probably makes sense to initially stick to yaml for data formats, since json 
doesn't ship with ruby, and to also allow executable facts to return either a 
plain string or yaml.

Note that we can do this without supporting any kind of overriding, but it'd be 
much better if we supported multiple (configurable?) fact directories, with a 
search path. Thus, if Facter shipped with /etc/facter.d/myfactname and you 
wanted to override it, you could do so by creating a new file and putting it in 
a higher-priority location rather than editing a file distributed with the core.


-- 
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.

Reply via email to