feat(vault): support custom metadata. #68
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.
Context
Vault 1.9 will support custom metadata with constraints.
Each secret also has version-agnostic metadata. This data can contain a
custom_metadata
field ofuser-provided key-value pairs. Vault imposes the following custom metadata limits:
Sample
Instrument your secret specification by adding
annotations
and/orlabels
By default, with
--with-metadata
flag, secret metadata are stored in a reserved key inside the secret dataIf you are using >Vault 1.9, you can use
--with-vault-metadata
to enablecustom_metadata
storageWhen you need to restore the Bundle from Vault, you have to use
--with-metadata
or--with-vault-metadata
flag to pull metadata from secret storage and rebuild Bundle package information.Reference(s)