Am Mittwoch, den 04.03.2020, 10:58 +0100 schrieb Martin Alfke:
Yes, both deliver same results.
I prefer the second option (using paths)
The first option is useful in case that you need to set hierarchy individual
settings.
Great. Thanks a lot.
Bye...
Dirk
--
Dirk Heinrichs
Senior Systems
Hi Dirk,
> On 4. Mar 2020, at 09:12, Dirk Heinrichs wrote:
>
> Am Mittwoch, den 04.03.2020, 07:56 + schrieb Dirk Heinrichs:
>
>> I assume these two are equivalent:
Yes, both deliver same results.
I prefer the second option (using paths)
The first option is useful in case that you need to
Am Mittwoch, den 04.03.2020, 07:56 + schrieb Dirk Heinrichs:
I assume these two are equivalent:
Once again, with better indentation:
hierarchy:
- name: "Per-kernel data"
path: "kernel/%{facts.kernel}.yaml"
- name: "Common data"
path: "common.yaml"
hierarchy:
- name:
Am Dienstag, den 03.03.2020, 15:12 +0100 schrieb Henrik Lindberg:
Hope that helps.
Yeah, thanks a lot. Got another one, though.
I assume these two are equivalent:
hierarchy:
- name: "Per-kernel data"
path: "kernel/%{facts.kernel}.yaml"
- name: "Common data"
path: "common.yaml"
hierarchy:
-
On 2020-03-03 11:17, Dirk Heinrichs wrote:
Hi,
while reading through the documentation about migrating to Hiera v5, the
following questions came to my mind:
* Can /hiera.yaml be a symlink? Our setup is as such that
each subdirectory (modules, manifests, hiera) of each environment is
Hi,
while reading through the documentation about migrating to Hiera v5, the
following questions came to my mind:
* Can /hiera.yaml be a symlink? Our setup is as such that each
subdirectory (modules, manifests, hiera) of each environment is a clone of a
Git repository, with different
