You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
The text was updated successfully, but these errors were encountered: