Hi Peter,
It all depends wher you use variables.
In manifests, it is best practice to scope facts @ top scope (::), if
you really want to use the fact
you can do something like this :
ipaddress => 192.168.10.0 (the fact)
class { 'x':
$ipaddress = '10.0.0.0'
notify { "fact = ${::ipaddre
Hi Johan,
Thanks for the suggestion, unfortunately it did not work.
It seems that using a scope file
(http://docs.puppetlabs.com/hiera/1/command_line.html#json-and-yaml-scopes)
doesn't load the facts into the global scope. Could this be a hiera
command line bug?
If I change the hiera.yaml hi
Hi,
Could it be something stupid like
---
fqdn: puppet.koewacht.net
in your facts.yaml ?
I generated my facts.yaml from facter -y
Grts
Jo
On 01/09/2014 12:29 PM, Peter wrote:
Hi List,
I am experimenting with different hiera hierarchy's through the hiera
command line. I am passing in dif
