I also went back and looked at my tweaks to R.I's code, and it looks like I
was/am actually using a value from 'scope' that gets defined by my code :(
So I've got a defined type that looks like [1], which sets the value of
'module' to either the value provided, or 'caller_module_name' if not
p
Henrik
Cheers for the quick response. I haven't tried this scenario on 4.x, and I
doubt I will for quite a while...
OK, so to elaborate on the namespace thing, and possibly try and explain
what I'm trying to achieve...
I've got module_a, which uses DIM, and defines a key of 'module_a::key_a'
On 16/05/16 13:00, Gavin Williams wrote:
Morning all...
I've hit a bit of an issue with our usage of Data-In-Modules (DIM)
provided by ripienaar/module_data with Puppet 3.7.x and was wondering
what the best option might be...
TL;DR: How can I change the DIM Hiera lookup scope to use the correct
Morning all...
I've hit a bit of an issue with our usage of Data-In-Modules (DIM) provided
by ripienaar/module_data with Puppet 3.7.x and was wondering what the best
option might be...
TL;DR: How can I change the DIM Hiera lookup scope to use the correct
module?
Currently, we have the foll
