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 because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/6d1807d9-ab03-4ae0-ab77-ca7dd864f4cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
