We're using the puppetlabs puppet rpms, on redhat 6.
puppet server version: 3.1.1
I wanted to start using hiera for some databinding type purposes.
I set up a /etc/puppet/hiera.yaml, pointing to a special hieradata
directory...but clients were not seeing the values I populated.
So I made a very stripped down version of a manifest for testing, with
$domain=hiera("philcheck::value")
file {"/tmp/hieratest":
ensure => present,
content=>"$domain \n",
}
The only way it found any hiera-set value, was if I put it in
/var/lib/hiera/common.yaml
Which is rather odd, because the autogenerated /etc/hiera.yaml does not
mention "common". it mentions "global".
And the config I created in /etc/puppet/hiera.yaml, I deliberately abused
to reference "common-p", instead of "common".
Yet it still pulls from "common". While ignoring any varient of
/var/lib/hiera/${hostname}.yaml
What's going on and how can I fix this please?
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
