On 20/03/17 16:03, Darragh Bailey wrote:
Hi,
Looking at how our hiera levels are already exploding due to some
preferences, I'm wondering how others describe use hiera.
We have a preference to group related data within separate files,
however some colleague concerns about using
Hi Rob,
Thanks for some of the suggestions, I suspect part of our problem is that
we have multiple applications/services deployed per node using docker
containers.
We probably can't easily map a single role per machine because we want to
be able to move the application/services between
If you're looking up hiera data based on the calling class, I'd question
whether that's useful to split out to hiera at all - every instance of the
class would get the same values, right? And would you really want ALL nodes
that `include jenkins` to get the same jenkins server? Even if they're in
Hi,
Looking at how our hiera levels are already exploding due to some
preferences, I'm wondering how others describe use hiera.
We have a preference to group related data within separate files, however
some colleague concerns about using '%{module_name}' and '%{calling_class}'
means that for
