refactor: broadly refactor Vault client #270
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit broadly refactors the Vault backend to improve K/V lookup for both V1 and V2 KVs. It properly leverages the
prefix
configuration for the Secrets Engine path and accomodates the differences between the KV v1 and KV v2 endpoints, specifically the use ofdata
in the secret path. This returns the Vault backend back to pathing parity with the other backends. It also means this commit is a breaking change and is not backwards compatible with configurations that use the more explicit pathing.This commit also resolves issue #244