Problem:
So, currently as has been explained to me, doing a lookup with keys
containing "." chops the key at first "." because of scoping and
namespace. This makes file-based lookups impossible (as far as I can
tell). I would like to be able to use HTTP or other backends to serve
files, which by their very nature WILL contain file extensions.
lookup('/path/to/somefile.txt') will lookup "/path/to/somefile"
Expectation:
While I understand that changing the very function of lookup to
accomodate this is out of scope, I would still think that providing a way
to tell lookup to NOT chomp or namespace the lookup would be appropriate?
Something like "lookup('/path/to/somefile.txt', scope=false)"... In this
manner, the user and more specifically, each lookup call can determine
whether or not to include the dotted key.
Is this something we could push forward? How would I go about doing that ?
--
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/c4e8c719-5367-4da4-a7d5-a95f0684e5ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
