Since a lot of people using this tool will be developers with MacBooks and not hardcore *nix users, it’s probably a good choice to ignore that convention.
I disagree, as the average vault user is likely someone familiar with Unix (though there is a Windows binary). Here is an example that I just ran on my machine.. very silent.
$ mkdir source
$ cd source
$ touch file
$ rm file
$ $ rm file
$ echo $?
$ 0
I picked this up at http://www.rsync.net/resources/howto/remote_commands.html for running commands over ssh and not seeing the console output.
We should be creating stable and predictable programs so that we can maintain users' trust. Otherwise we have to introduce hand-holding which degrades everyone's experience through extra cognitive overhead and user interaction.
cron adopts this philosophy in that you get an email if there is any output at all.
There is a tool called chronic which you can use as a wrapper which captures stdout and only ouput if the return code is an error:
$ chronic vault kv undelete -versions=2 secret/my-secret
$
That is:
should instead be: Also, the screenshots on the Vault OSS UI Introduction page [0] are completely unintelligible.[0]: https://www.hashicorp.com/resources/vault-oss-ui-introductio...