Niels de Vos a5211dcf0e util: allow configuring VAULT_BACKEND for Vault connection ... It seems that the version of the key/value engine can not always be detected for Hashicorp Vault. In certain cases, it is required to configure the `VAULT_BACKEND` (or `vaultBackend`) option so that a successful connection to the service can be made. The `kv-v2` is the current default for development deployments of Hashicorp Vault (what we use for automated testing). Production deployments default to version 1 for now. Signed-off-by: Niels de Vos <ndevos@redhat.com> (cherry picked from commit 82557e3f34)		2021-08-10 10:08:16 +00:00
..
cephfs	cleanup: correct nolint directive listing format	2021-04-09 07:24:47 +00:00
controller	rbd: take lock when reconciling the PV	2021-04-07 11:46:27 +00:00
csi-common	util: add nil check to default ControllerGetCapabilities()	2021-04-09 10:12:48 +00:00
journal	rbd: store csi.storage.k8s.io/pvc/namespace metadata as Owner	2020-12-09 13:58:48 +00:00
liveness	util: replace klog with util logger in liveness.go	2020-08-19 14:38:12 +00:00
rbd	cleanup: prevent panic in cleanUpSnapshot	2021-06-25 12:12:52 +00:00
util	util: allow configuring VAULT_BACKEND for Vault connection	2021-08-10 10:08:16 +00:00