54c414abb2
One thing that has been a point of confusion for users is Vault's
response when deleting a key that does not actually exist in the system.
For example, consider:
$ vault delete secret/foo
Success! Deleted 'secret/foo'
This message is misleading if the secret does not exist, especially if
the same command is run twice in a row.
Obviously the reason for this is clear - returning an error if a secret
does not exist would reveal the existence of a secret (the same reason
everything on S3 is a 403 or why GitHub repos 404 instead of 403 if you
do not have permission to view them).
I think we can make the UX a little bit better by adding just a few
words to the output:
$ vault delete secret/foo
Success! Deleted 'secret/foo' if it existed
This makes it clear that the operation was only performed if the secret
existed, but it does not reveal any more information.
|
||
|---|---|---|
| .. | ||
| helpers | ||
| scripts | ||
| source | ||
| config.rb | ||
| config.ru | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| Makefile | ||
| packer.json | ||
| README.md | ||
| Vagrantfile | ||
Vault Website
This subdirectory contains the entire source for the Vault Website. This is a Middleman project, which builds a static site from these source files.
Contributions Welcome!
If you find a typo or you feel like you can improve the HTML, CSS, or JavaScript, we welcome contributions. Feel free to open issues or pull requests like any normal GitHub project, and we'll merge it in.
Running the Site Locally
Running the site locally is simple. Clone this repo and run make dev.
Then open up http://localhost:4567. Note that some URLs you may need to append
".html" to make them work (in the navigation).