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 at present. A backend implementation can however (in the next release of hiera) participate in resolving the subkey lookup. This was added for backends where the top key would result in something huge being delivered over the wire, only to then be navigated to a single value. The addition makes it possible for the backend to get the entire key "a.b.c" and to deal with it appropriately.
To use that, you would need to create a custom variant of YAML, JSON or whatever you are using, and then ignore the subkeys and instead use them as regular keys.
- henrik -- Visit my Blog "Puppet on the Edge" http://puppet-on-the-edge.blogspot.se/ -- 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/n46gs5%24hsv%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
