Wed, Feb 15, 2017 at 10:19 PM Ben Hines <bhi...@gmail.com >
> wrote:
>
>> I would be really cool if warnings could be disabled (And re enabled)
>> from code, like like pragmas in C++. That would let me keep the undefined
>> variables warning where it's needed, but i
I would be really cool if warnings could be disabled (And re enabled) from
code, like like pragmas in C++. That would let me keep the undefined
variables warning where it's needed, but ignore for other areas. (like
third party modules i may not care about)
In my case, i am using hiera lookup
com
> wrote:
> On 08/02/17 17:55, Ben Hines wrote:
>
>> Perhaps this is just a bug, but does %{calling_class} function with
>> Hiera 5? I haven't been able to get it to function. Perhaps it has a
>> new syntax?
>>
>>
> It is deliberately not supported in the
Perhaps this is just a bug, but does %{calling_class} function with Hiera
5? I haven't been able to get it to function. Perhaps it has a new syntax?
Notice it's blank:
==> test: Hierarchy entry "calling_class"
==> test: Path
Howdy,
My organization has a pre-existing hiera configuration which uses
{calling_class}.yaml configuration files, like:
classes/base::openldap.yaml
Which get pulled into hiera via this path in the hierarchy.
:hierarchy:
...
- %{environment}/classes/%{calling_class}
This does not work on
