On Monday 01 September 2014 05:39 AM, Atom Powers wrote:
Poli, that doesn't really solve the problem since the variable values
could still come from many places. (Puppet also does some of that
lookup automatically, although not as deep.)
Yes, though my primary goal is simply to reduce unnecessary duplication.
A single added configurable template parameter currently ends up being
in three places even before bringing in hiera, which is
pretty bad.
This whole thing was brought about by my writing parameterized classes
for some of our
internal custom services that have dozens of options in their config
templates, and the manifest file is just
a sea of parameter names.
I think I'm just going to start putting defaults in the class
declaration param list unless they explicitly
require logic to compute, in which case they'll come from the params.
This may be relevant:
https://github.com/ripienaar/puppet-module-data/
This looks really cool! Thanks for the reference.
-Taj.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/54041A92.1020708%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
