|
At present, the explain output will just show how a lookup proceeds using a given configuration. It does not show how that configuration came into existence. So, for instance, when using a path, it will show both the original and the effective path which is the result of expanding all interpolations in the original. It will however not include all lookup's that were made in order to resolve those interpolations.
I think the best way to resolve this is to introduce an additional option that would make the explainer produce output on how the all configurations are built up from their respective hiera.yaml hash. It's not trivial though. In order for such output to make sense, it's probably necessary to disable caches and triggers for invalidating them, which in turn might change the behavior slightly.
Another option is to enforce strictness using the --strict option so that invalid mapped paths causes logged warnings or errors in the regular puppet log. That would be far simpler and not require additional control from the user.
|
