Open riupko opened 10 months ago
We ran into this too. I can understand the argument for throwing authentication errors while suppressing authorization and connection errors, but I would think most of the time Optional is used when a setting isn't required or is behind a feature flag, so we don't want any errors thrown.
Having the following configuration
and reference to existing Vault Name
I am getting the following runtime exception
Due to enabled="optional" I expect this error to be suppressed and environment is working based on SimpleJson configuration only.