Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(vault): support custom metadata. #68

Merged
merged 6 commits into from
Sep 21, 2021
Merged

Conversation

Zenithar
Copy link
Contributor

@Zenithar Zenithar commented Sep 20, 2021

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 of
user-provided key-value pairs. Vault imposes the following custom metadata limits:

Limit
Number of custom metadata key-value pairs 64
Custom metadata key size 128 bytes
Custom metadata value size 512 bytes

Sample

Instrument your secret specification by adding annotations and/or labels

image

By default, with --with-metadata flag, secret metadata are stored in a reserved key inside the secret data

image

If you are using >Vault 1.9, you can use --with-vault-metadata to enable custom_metadata storage

image

When 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.

image

Reference(s)

@Zenithar Zenithar self-assigned this Sep 20, 2021
@Zenithar Zenithar marked this pull request as draft September 20, 2021 17:50
@Zenithar Zenithar added the enhancement New feature or request label Sep 20, 2021
@Zenithar Zenithar marked this pull request as ready for review September 21, 2021 13:15
@Zenithar Zenithar merged commit efa2a81 into main Sep 21, 2021
@Zenithar Zenithar deleted the feat_vault_custom_metadata branch October 23, 2021 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant