Hi Robert,
Thanks for the link, I remember now. That indeed makes sense as code
is not obstructed by 'hiera' calls.
Cheers,
Luke
On 1 July 2013 10:42, Robert Frank <[log in to unmask]> wrote:
> Hi,
>
> Alessandra is referring to the automatic parameter lookup, see here:
> http://docs.puppetlabs.com/hiera/1/puppet.html#automatic-parameter-lookup
>
> This way you can keep your classes / defines free of hiera calls, but still
> define your parameter values in hiera. This only works for simple hiera
> calls though, not for hiera_hash, hiera_array, hiera_include.
>
> Cheers,
>
> Robert
>
>
> On 01/07/13 09:58, L Kreczko wrote:
>>
>> Hi,
>>
>> However, params.pp has the benefit that new users can see the set of
>> "sensible" values for the module.
>> If one wants to use hiera it can be combined here with the defaults.
>> @Alessandra: Could you please give an example of how you use hiera
>> completely transparent? I am having trouble understanding what you
>> mean.
>>
>> Cheers,
>> Luke
>>
>> On 1 July 2013 08:10, Alessandra Forti <[log in to unmask]> wrote:
>>>
>>> On 19/06/2013 10:45, Alessandra Forti wrote:
>>>
>>> Hi,
>>>
>>> Robert is just finishing the upgrade to puppet 3.2 in Manchester and we
>>> are
>>> also using hiera - which in 3.x will be more transparent - and templates.
>>>
>>> after actually using it rather than reading docs... using hiera in puppet
>>> 3.2 is completely transparent and moving to puppet 3.2 is highly
>>> reccomended
>>> if you want to put all your data structures in 1 place. You don't even
>>> need
>>> params.pp classes anymore to separate the code and hiera calls and the
>>> data
>>> structures can be arbitrarily complicated. :-)
>>>
>>> cheers
>>> alessandra
>>>
>>
>>
>>
>
--
******************************************************
Lukasz Kreczko +44 (0)117 928 8724
CMS Group
School of Physics
University of Bristol
******************************************************
|