On 2015-08-12 1:46, Adrian Muraru wrote:
With the addition of subkeys lookup, e.g. hiera('a.b.c'), those yaml
configuration files already including top level keys with a "." in the
key name are rendered invalid.
Is there a way to disable subkey lookup support on demand for a given
backend?
Not
With the addition of subkeys lookup, e.g. hiera('a.b.c'), those yaml
configuration files already including top level keys with a "." in the key
name are rendered invalid.
Is there a way to disable subkey lookup support on demand for a given
backend?
thanks,
adrian
--
You received this message
