I have a defined resource type (let's call it `widget`) which gets defined
multiple times per customer. Each customer has their own default
configuration values for their widgets, and these are very rarely (but
occasionally) overridden. I'd like to minimize the amount of typing
necessary when someone adds a new widget to the systems, so I'm thinking of
a Hiera structure similar to this:
widget_defaults:
customer1:
colour: green
size: big
outline: vague
customer2:
colour: blue
size: big
outline: crisp
widgets:
customer1:
foo:{}
bar:
colour: violet
baz:{}
customer2:
froop:{}
vroom:{}
blargh:
outline: circular
This will require multiple hiera lookups inside the profile that
instantiates the resources though, in order to merge the defaults with any
override values. Is there a more idiomatic way to deal with something
like this?
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/f90c1a2e-d597-4594-b06f-3051e34641fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
