Closed jason-riddle closed 3 years ago
Hi, thanks for the issue. vault
was the original name of the command and only very recently was it changed to vault-cli
(https://github.com/peopledoc/vault-cli/issues/89) (EDIT I just realized the doc describes master, but I haven't released it yet into a proper version ! Will do this asap!), but we kept the old name for compatibility's sake. That's for the why. We plan to remove the old alias someday but doing it right now would likely break all existing users :/
Now to the "can this be reverted", I'm afraid the best I can suggest is to
vault
command by full pathrm /.local/bin/vault
which will leave you with vault-cli
for this tool and vault
for the official tool.I'll leave the ticket open until I:
vault-cli
that supports vault-cli
as the command name, which should be in a few minutesany updates on this issue? I think users can be notified of the breaking change?
Yep, I've started making sure our internal users won't suffer from the change, and I should be able to make a new release once that is done.
Ok, we should be good to proceed. Do you want to do the PR @abebars ?
The documentation says to install vault-cli with
pip install vault-cli
. However, the script is available asvault
and because~/.local/bin
comes first in my path, it is overriding the vault CLI binary, making it impossible to use both tools. Steps to reproduce (using pipx):Why is this the case? Also, can this be reverted?