Skip to content
This repository has been archived by the owner on Mar 27, 2019. It is now read-only.

"generic" secrets backend is now named "kv" #197

Closed
curlywurlycraig opened this issue Sep 29, 2017 · 3 comments
Closed

"generic" secrets backend is now named "kv" #197

curlywurlycraig opened this issue Sep 29, 2017 · 3 comments
Assignees

Comments

@curlywurlycraig
Copy link

curlywurlycraig commented Sep 29, 2017

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.

@curlywurlycraig curlywurlycraig changed the title generic secrets backend is now named kv "generic" secrets backend is now named "kv" Sep 29, 2017
@djenriquez
Copy link
Owner

Hmm I wonder if this is whats going on with #190.

@djenriquez
Copy link
Owner

@curlywurlycraig, this has been merged in, give it a shot at djenriquez/vault-ui:latest. If it looks good to you, please close the issue.

@djenriquez
Copy link
Owner

Closing per #198.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants