Hi,
I'm trying to do something with Hiera, whereby the 'default' configuration
for a class is within it's role/profile manifest, which can then be
overridden on a node specific basis by hiera.
As an example;
class profile::base {
class { '::ntp':
servers => ['a', 'b', 'c', 'd']
}
}
node 'blah.com' {
include profile::base
}
hieradata/nodes/blah.com.yaml:
---
ntp::servers:
- 0.uk.pool.ntp.org
- 1.uk.pool.ntp.org
However, I've noticed that hiera's behaviour seems to be that if a
parameter is set like I do for the ntp::server param in the ntp class, it's
not looked up (all the other NTP params are looked up in hiera, except for
servers). Whereas if I just do:
class profile::base {
class { '::ntp': }
}
The server parameter is now looked up from hiera.
Is this intended behaviour?
Thanks,
Rob
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/71878f56-55a3-409b-adaf-4b5b96f968d2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
