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
{{ message }}
This repository has been archived by the owner on Mar 27, 2019. It is now read-only.
As per the changelog for Vault, the generic secrets backend is now named kv. It seems that vault-ui doesn't look for secrets mounted as the type kv, as when we have created secrets via. the CLI mounted as type kv, they are not visible in the vault-ui sidebar.
Expectation: Secret backends with type kv should be visible in the Vault sidebar. Result: Secret backends with type kv are not visible in the Vault sidebar.
Furthermore, it is not possible to create new secret backends with type kv from the UI. Although kv and generic are functionally the same, it's worth keeping up with Vault changes and switching to the use of kv.
The text was updated successfully, but these errors were encountered:
curlywurlycraig
changed the title
generic secrets backend is now named kv
"generic" secrets backend is now named "kv"
Sep 29, 2017
As per the changelog for Vault, the
generic
secrets backend is now namedkv
. It seems thatvault-ui
doesn't look for secrets mounted as the typekv
, as when we have created secrets via. the CLI mounted as typekv
, they are not visible in the vault-ui sidebar.Expectation: Secret backends with type
kv
should be visible in the Vault sidebar.Result: Secret backends with type
kv
are not visible in the Vault sidebar.Furthermore, it is not possible to create new secret backends with type
kv
from the UI. Althoughkv
andgeneric
are functionally the same, it's worth keeping up with Vault changes and switching to the use ofkv
.The text was updated successfully, but these errors were encountered: