Open s-vitaliy opened 2 years ago
Hi @s-vitaliy can you put an example on what you are trying to achieve? If I understood correctly, what you'd like is not having to specify the keys in the vault path at all, so secrets-manager
will actually pull the keys and create a k8s secret with the same key names? Is that what you're suggesting?
Hi @fcrespofastly, you are right. Because of this, we could not use your secret manager and we considered to use external secrets operator instead: https://external-secrets.io/v0.5.8/provider-hashicorp-vault/#multiple-nested-values
Hi,
We would like to utilize your secret manager to use in our kubernetes cluster, but we have faced a trouble: the custom resource definition in secret manager reuqires to map keys from Vault's secret object to kubernetes secret object.
We need to sync the secrets from Vault to kubernetes when user updates the Vault secret manually, without need to commit any configuration changes in repository.
Is it possible to create 1-to-1 mapping from Vault secret object to kubernetes secret object with your tool?