| yes sure my backend can (and does already) raise am error that is not `not_found` and abort the whole lookup chain, but that seems like a hack. My backend is already raising a not_found exception as documented when the key is not found. The problem is how this exception is treated by hiera. The lookup function just treats it as an empty string which for a custom backend is most likely the completely wrong behaviour. Puppet lookup() (when not provided with an explicit default) treats it as a compilation aborting error. This is the behavior I would like for the hiera lookup. Sure for backward compatibility the default hiera lookup must probably stay, but it could get a strict argument or a completely new function which has same not_found behavior as puppet. |
