Hi,
That would define $primary_group as a variable, not as a fact. Indeed, what I
want to do is:
:backends: - puppet
:hierarchy: - %{primary_group}
:puppet:
:datasource: data
And that requires primary_group to be a fact.
Any other ideas?
Thanks!
Pablo
Ahhh your right, that's not going to work. Ok...
I know that some people use %{calling_class} and %{calling_module} in
their hiera.yaml (I don't) so that means the hiera Puppet function must
get some of the Puppet catalog's state that's not just Facts. In this file:
On Fri, Mar 23, 2012 at 3:42 AM, Pablo Fernandez pablo.fernan...@cscs.chwrote:
**
Dear all,
This is a continuation of another thread, but I think the question
diverged enough to create a new one.
I have a hiera hierarchy like this:
:hierarchy:
- %{fqdn}
- %{secundary_group}
-
On second-thought, #3 would be out of the question if you wanted to use
%{primary_group} as a hierarchy level in Hiera. You will need to either
write a fact to determine the group based on something atomic about the
system or do something at provision time. Do you have this
Hi,
I've just run into a small glitch with Hiera.
I have a YAML file that has a definition like this:
puppet_agent_splay: false
but the run fails because of
err: Could not find data item puppet_agent_splay in any Hiera data
file and no default supplied at
Hi Lars,
Can you file a ticket against this in our redmine system if one doesn't
already exist? We have a similar issue here --
http://projects.puppetlabs.com/issues/10590
-Gary
On Sat, Mar 24, 2012 at 8:52 PM, Lars Francke lars.fran...@gmail.comwrote:
Hi,
I've just run into a small glitch
