Re: [Puppet Users] Style - hiera/params/puppet/template

2014-09-04 Thread Christopher Wood
On Mon, Sep 01, 2014 at 12:34:50PM +0530, Sirtaj Singh Kang wrote: 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

Re: [Puppet Users] Style - hiera/params/puppet/template

2014-09-01 Thread Sirtaj Singh Kang
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

Re: [Puppet Users] Style - hiera/params/puppet/template

2014-08-31 Thread Atom Powers
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.) This may be relevant: https://github.com/ripienaar/puppet-module-data/ I still used parameterized classes with an

[Puppet Users] Style - hiera/params/puppet/template

2014-08-30 Thread Sirtaj Singh Kang
Greetings all, In the pre-hiera days, it was commonly recommended to write classes with params like this: class my_class::params { $config_param = 'default value' } class my_class ( $config_param = $myclass:params::config_param ) inherits myclass::params { ... } However, now

Re: [Puppet Users] Style - hiera/params/puppet/template

2014-08-30 Thread Poil
Hi, //I use params_lookup (lib from puppi) https://github.com/example42/puppi/blob/master/lib/puppet/parser/functions/params_lookup.rb it lookup in this order (first match is returned) - Hiera backend (if present) for modulename_varname - Hiera backend (if present) for varname (if second