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

Allow patching existing secret #8

Open
joonvena opened this issue Aug 4, 2023 · 0 comments
Open

Allow patching existing secret #8

joonvena opened this issue Aug 4, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@joonvena
Copy link

joonvena commented Aug 4, 2023

What problem are you facing?

I would like to store secrets created by composition to the Vault. Developer would also handle adding new secrets to the kv path manually from the Vault UI. This would mean that if crossplane managed Vault Secret would change the update would delete all the user added secrets.

How could Upbound help solve your problem?

Vault supports patching of secrets using JSON merge patching that will only touch the specific secrets defined in the request and leave other secrets alone. It would be nice if the provider could support the patching behaviour. Here is link to the Vault documentation that explains how the merge patching works:

https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v2#patch-secret

@joonvena joonvena added the enhancement New feature or request label Aug 4, 2023
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

No branches or pull requests

1 participant