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.
Resolves #115 and based on code from #122. You can put arbitrary JSON data into
kv
's values (and theoretically other secret engines could do the same) using a JSON file and a command likevault kv put secret/test @test.json
, and this PR allowsvault-csi-provider
to specifically select that JSON data without having to escape your secret JSON into a big ugly string when storing it in Vault.This PR does not address arbitrary paths within the JSON though. Vault's API itself enforces that the top-level data object is a map, and users should be able to select any single top-level key from that object.
Strings remain special-cased so that we continue to write string values without wrapping them in quotes.