vault: add KV v2 support for custom mount paths#168
Open
Nivedita-coder wants to merge 1 commit into
Open
Conversation
|
|
Nivedita-coder
force-pushed
the
supportkv2
branch
2 times, most recently
from
ae27053 to
3dcd83d
Compare
Nivedita-coder
force-pushed
the
supportkv2
branch
from
3dcd83d to
451c733
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
vault: fix KV v2 handling by separating mountPath from KV version
Previously KV v2 was only used when mountPath == "kv2".
This change introduces KVVersion to correctly support KV v2
engines mounted under arbitrary paths, and updates tests accordingly.