On May 7, 2012, at 12:47 PM, Christopher Wood wrote:
> Wrapper script (similar concept for anywhere with a yaml reader):
Still have to *write* the YAML files.
> Out of nosiness, how do you handle the edgier cases in your manifests? For
> example, how everything is a standard syslog client, except for this host
> which is loghost, and these couple of clients which all do different things
> with syslog?
We would have the syslog module have all the "common"
files/packages/services/etc. declared, and then simply do something like:
if ($fqdn =~ /^syslog/)
{
..... log host specific stuff .....
}
else
{
..... NON-log host specific stuff .....
}
doesn't seem like rocket science, and makes it clear, all in one place, what's
"common", and what's "special".
Puppet provides some wonderful decision-making capabilities in the manifests
themselves, I've yet to see any need to have some ugly machine-readable
formatted file to solve a problem.
But I *have* seen the parts of our organization that DO use Hiera complaining
loudly that they can't easily figure out which of a slurry of YAML files is
changing some setting/variable to a value they're not expecting.
Cheers,
D
--
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.
