All,
Just started to use mcollective. I found an example at
http://www.semicomplete.com/blog/geekery/puppet-facts-into-mcollective.html:
file {
"/etc/mcollective/facts.yaml":
ensure => file,
content => inline_template("<%= scope.to_hash.reject { |k,v| !(
k.is_a?(String) && v.is_a?(String) ) }.to_yaml %>"),
require => Package["mcollective"];
}
... that dumps all the variables in scope to /etc/mcollective/facts.yaml.
Great... except that it only dumps the variables currently in scope. I think
I'd like a little more control. Should I just use a template that contains
specific variables? Not really sure what the best approach is here.
What I would actually like is to have multiple fact files, each with a
different sets of facts, and have mcollective aggregate them all together.
Doug.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
