Add write support for vaultkv secrets #958
Closed
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.
Fixes issue #786, #854
Proposed Changes
VaultClient
andVaultServer
to simplify authentication and testing a bit and reduce code redundancy.hvac
to version1.0.2
and replace depricated api functionsExamples
?{vaultkv:path/to/ref:mount_in_vault:path/in/vault:key||random:str}
?{vaultkv:path/to/ref:::key||random:str}
would create / lookup a secret withmount=secret
andpath/in/vault=path/to/ref
CLI
Use
kapitan refs --write vaultkv:test/secret -f test/secret/file --refs-path refs/path --vault-mount testmount --vault-path test/path --vault-key testkey
to write your secret stored intest/secret/file
to kapitan ref engine.Replaced / Outdated Pull-Requests:
1.0.2
#957Contributed by