----- Original Message -----
> From: "Pieter van de Bruggen" <pie...@puppetlabs.com>
<snip>
>
> * How should we integrate hiera_array() and hiera_hash() ?
> * How should we integrate hiera ’s “default” and “override”
> parameters?
> * How should we handle overlaps between data supplied by Hiera
> and data supplied in a parameterized class include?
Given:
class foo($something="default") { }
I think the plan was that there would be a priority order as below:
- someone wrote in a manifest: class{"foo": something => something}
- an ENC supplied the values for something on the class foo
- someone did "include foo" or class{"foo": } this would consult hiera
- if hiera does not have an answer it would default to "default"
This gives people with more complex needs than those matched by hiera
the ability to use ENCs and get exactly the data model they desire as
well as people who do not want any magical data lookup for some class
the ability to hard code values.
And at the same time it lets module authors provide out of the box
defaults that work without placing a load on module users where they
might have to read every class and set hiera values for every argument
before they can use a class if all they wanted was the default out of
the box behaviour.
Does this sound sane?
> If you’re interested in test-driving the new functionality for
> yourself, checkout out the master branch of the Puppet repository on
> Github , install Hiera (with gem install hiera ) and make the
> following configuration changes:
>
> * Set data_binding_terminus to hiera
> * If you have a Hiera configuration file, set hiera_config to
> point to it.
> * If you don’t, create a file in ${confdir}/hiera.yaml with these
> contents:
>
>
> :backend:
>
> - yaml
>
> :yaml:
>
> :datadir: $confdir/data
>
> :hierarchy:
>
> - %{certname}
>
> - %{environment}
>
> - global
>
> This sets up a default hierarchy that looks for values in
> ${confdir}/data , first in the ${certname}.yml file, then in the
> ${environment}.yml file, then in global.yml .
These should probably %{::certname} etc right?
--
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.
