We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Shell completion list/put/patch for KV v2 paths is always empty
To Reproduce Steps to reproduce the behavior:
- kvv1 (mount of type kv, version 1) - a - b - kvv2 (mount of type kv, version 2) - c - d
vault kv delete kvv1/<tab>
kvv1/a/b
vault kv delete kvv2/<tab>
Expected behavior I would expect that the kvv2 suggestions are not empty and contain kvv2/c/d, similarly to what I get for kvv1
kvv2/c/d
kvv1
Environment:
vault status
vault version
Linux vault-0 5.10.109+ #1 SMP Tue May 24 09:08:48 UTC 2022 x86_64 Linux (running on kubernetes pod)
The text was updated successfully, but these errors were encountered:
Hi @georgethebeatle , thanks for opening the PR! I've left a few comments on it, but the functional code changes look good!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Shell completion list/put/patch for KV v2 paths is always empty
To Reproduce
Steps to reproduce the behavior:
vault kv delete kvv1/<tab>
, I getkvv1/a/b
as a suggestion.vault kv delete kvv2/<tab>
, the suggestion list is empty.Expected behavior
I would expect that the kvv2 suggestions are not empty and contain
kvv2/c/d
, similarly to what I get forkvv1
Environment:
vault status
): 1.10.3vault version
): 1.12.0Linux vault-0 5.10.109+ #1 SMP Tue May 24 09:08:48 UTC 2022 x86_64 Linux (running on kubernetes pod)
The text was updated successfully, but these errors were encountered: