No custom lookup function allowed #162
Labels
bug
Something isn't working
Comments
|
I am not sure how and if hdm can solve this. From what I gather, I custom lookup functions means that someone is using a fully custom backend, which (from hdm's point of view) could be anything. And of course hardcoding this one instance to mean eyaml makes no sense, as it might mean something completely different for another user (especially since the name is very generic). The only thing I can imagine right now, is that we add a configuration option in custom_lookup_function_mapping:
puppet_function_lookup_key: eyaml |
|
Please implement using the solution you described. |
oneiros
added a commit
that referenced
this issue
Jul 5, 2023
We do not (and cannot support) custom lookup functions per se, but in case they map cleanly to an existing backing, e.g. eyaml, this allows to specify this mapping, so everything should then work as expected.
tuxmea
added a commit
that referenced
this issue
Aug 10, 2023
* Upgrade dependencies. Latest security fixes for rails plus a bunch of minor updates. * Allow custom lookup functions #162 We do not (and cannot support) custom lookup functions per se, but in case they map cleanly to an existing backing, e.g. eyaml, this allows to specify this mapping, so everything should then work as expected. --------- Co-authored-by: Martin Alfke <tuxmea@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a customer who has a self written puppet lookup function:
puppet_function_lookup_keyHDM does show error 500 when we select a node.
I already found
app/models/hiera_data/hierarchy.rbhas a mapping of functions and return yaml, json or eyaml. In this case we should use eyaml.Is this possible to achieve?
The text was updated successfully, but these errors were encountered: