Vault 0.10 released

Post by onmai-xyz » Wed, Apr 11, 2018, 3:22 PM UTC

otp124 wrote: post #7

jrs95 wrote: post #6

Earlier quoted context omitted.

For your average user I think this is confusing and not good UX. 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.

> For your average user I think this is confusing and not good UX. 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

Silent, unless you go looking. The return value of the last executed command is available as $?.

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.

Post by dalore » Wed, Apr 11, 2018, 3:50 PM UTC

jlgaddis wrote: post #5

What happened to the old Unix philosophy about doing nothing on success (a.k.a. "Rule of Silence")? That is: $ vault kv undelete -versions=2 secret/my-secret Success! Data written to: secret/undelete/my-secret should instead be: $ vault kv undelete -versions=2 secret/my-secret $ Also, the screenshots on the Vault OSS UI Introduction page [0] are completely unintelligible. [0]: https://www.hashicorp.com/resources/vaul…

And yet a lot of unix tools also have a -q quiet mode to not output anything unless an error.

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
  $

Re: Vault 0.10 released

Re: Vault 0.10 released