Andrew, the oddity that I ran into was strictly because I made the
mistake of trying to specify a value for splay. Luckily enough it was
on my puppet dev machines so I had to go in manually and modify 4
diferent server configs.
It is definitely one of those grey lined areas that needs some
Hi
Glad you solved the issue.
If there is something you think would improve the documentation and make it
more clear for the next person, please add your notes.
it would also be nice to have the actual solution added to this thread.
Just in case someone else is having once this problem
2. Additional output formats - JSON, XML? (winces) - Facter already
outputs in YAML.
I'd vote for adding an optional output format to easily support shell
scripts:
Here is the shell compatible output of another tool I use:
set -A os_version_major 4
set -A os_version_minor
My external node classifier returns some arrays in the list of
parameters. Example output (names have been changed to protect the
innocent):
$ ./node_classifier a.b.com
--- %YAML:1.0
classes: [class1, class2, class3]
parameters:
hostname: a
name: a
domain: b.com
fqdn: a.b.com
group:
I guess one way would be to write a small custom function which gets an
array as an argument and returns an array of sources.
(didnt test :))
module Puppet::Parser::Functions
newfunction(:array2source, :type = :rvalue) do |args|
if args[0].is_a?(Array)
sources = Array.new
Oh and one other thing about 'facter.d' it'd be cool if there was some
way to say that a given fact (or set of facts) is cache-able. Perhaps
your fact is resource intensive to discover and doesn't change much.
It'd be cool to have a built-in facility in facter that says if you
just booted, find
