I am currently implementing the "hiera-http" custom backend written by
crayfishx located: "https://github.com/crayfishx/hiera-http";.
I have some custom classes that need to run through an iteration of hiera
hashes and perform lookups on the values of said hashes. As a result, I
would simply like to be able to have lookup('somestring') work from within
a module. When doing this, lookup fails to use the module-specific
hiera.yaml. I don't want ALL of my modules to use hiera-http as that is
clearly overkill and prone to latency and longer puppet runs. The only
workaround at the moment is to lookup("mymodule::somestring") which then
properly uses the module hiera.yaml and looks up the value in the
module-specific YAML.
As you can imagine, having an HTTP URI that contains "mymodule::somestring"
is not exactly clean, nor desired. Is there a way to specify the scope for
lookup to force it to use the proper hiera.yaml ?
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/b9e8b0dc-a4b4-426c-9caf-7987f2f4bcbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
