e
> nil/undef/etc.
>
> On Wed, Feb 15, 2017 at 10:19 PM Ben Hines >
> 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
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 pa
Okay, thanks! From reading changelogs in git it looked like it was intended
to be supported. It might be worth mentioning in the release notes.
Anyway in my case i can work around with module data.
thanks!
-Ben
On Fri, Feb 10, 2017 at 1:39 PM, Henrik Lindberg wrote:
> On 08/02/17 17:55,
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
"/tmp/vagrant-puppet/environments/myenv/data/classes/.y
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
