Commit graph

134 commits

Author SHA1 Message Date
Chris Maki 7b5978634f Update policies.html.md
Using the latest vault release, I was getting the following error when the policy used `write`:

Error: Error making API request.

URL: PUT http://0.0.0.0:8200/v1/sys/policy/secret
Code: 400. Errors:

* Failed to parse policy: path "secret/*": invalid capability 'write'

I think `create` is the correct new Capability.
2017-08-17 12:26:29 -07:00
Brian Kassouf 406396603a Fix a few links (#3188) 2017-08-16 10:27:12 -07:00
Jonathan Duncan 8e9f54fc70 Updated policy format to use capabilities keyword (#3063)
The `policy` key name is deprecated and has been replaced with `capabilities`.
2017-07-26 14:05:11 -04:00
Seth Vargo ce1808f77d Update Policies and Auth concepts pages (#3011) 2017-07-14 11:15:22 -04:00
Jeff Mitchell 40ef2e5c85 More cleanup
Ping #2894
2017-06-20 10:46:24 -04:00
Ken McVicker 3a354343af Update install.html.md
Updates list of commands with the output of 0.6.4.  Missing commands list, unwrap, capabilities, generate-root
2017-05-12 14:13:06 -06:00
Seth Vargo 6931bbd091
Links 2017-03-17 14:27:32 -04:00
Seth Vargo d4390d103e
/docs/http -> /api 2017-03-17 14:06:03 -04:00
Michael 412aad7c6e Updated doc to match real output (#2443)
Regards hashicorp/vault#2116
2017-03-06 10:39:34 -05:00
Frank Gevaerts 0044ea8917 Update hsm.html.md (#2381) 2017-02-16 07:25:22 -05:00
Jack Harris d5b1cc7ebe Add correct output to unmount documentation (#2352)
Simply adding the actual output of: 'vault unmount generic/'
2017-02-08 10:40:56 -05:00
windowsrefund 64e7e99755 prevent startup error when user has multiple private IPs configured locally 2017-01-03 15:24:11 -05:00
Jeff Mitchell ad5bdfa83c Update vs HSM text 2016-12-28 11:23:50 -05:00
James Turnbull 0b082bff42 Edits to the deploy guide 2016-12-14 11:17:50 -05:00
James Turnbull e2ef0b75b6 Edits to the authorization/acl guide 2016-12-14 11:11:14 -05:00
James Turnbull c47c8343b5 Edits to the authentication guide 2016-12-14 11:06:42 -05:00
James Turnbull 73ce47d0fe Formatting and language updates to help guide 2016-12-14 10:55:11 -05:00
James Turnbull ce6c0dcf95 Minor formatting fix to dynamic secrets guide 2016-12-14 10:51:56 -05:00
James Turnbull f1b5377e81 Updated some formatting and language in the secret backends doc 2016-12-14 10:46:14 -05:00
James Turnbull 73324e2cba Updated some formatting and language in the first secret doc 2016-12-14 10:39:45 -05:00
James Turnbull 3a981ae7b4 Updated some language and formatting in the dev-server guide 2016-12-14 10:34:52 -05:00
James Turnbull 49dd4f70df Edits to the install doc in getting started 2016-12-14 10:15:26 -05:00
James Turnbull 6df55a3126 Added next step to install section 2016-12-14 10:13:15 -05:00
Andrea Crotti d1c3367168 return code is 403 not 400 (#2128) 2016-11-25 06:47:27 -08:00
Em Smith 1812ce8d4a Change command examples for First Secrets #2116 (#2117)
These were discovered to be out of date as per https://github.com/hashicorp/vault/issues/2116
2016-11-22 12:44:17 -05:00
vishalnayak 260424244b s/localhost/127.0.0.1 2016-10-28 09:23:05 -04:00
vishalnayak 4ab6bd41c4 Using AppRole as an example. Removed 'root' policy being used in examples 2016-10-28 01:24:25 -04:00
vishalnayak 557bf45de6 Update the getting started API doc to not use 'root' policy 2016-10-11 16:07:48 -04:00
Jeff Mitchell f0203741ff Change default TTL from 30 to 32 to accommodate monthly operations (#1942) 2016-09-28 18:32:49 -04:00
Jeff Mitchell 96afb1d27a Update getting started docs since root can no longer be used from github 2016-09-26 13:09:26 -04:00
John c39eeecaea tip to override VAULT_ADDR in getting started guide (#1915) 2016-09-23 19:34:07 -04:00
Michael Warkentin 14f2a673e2 Out of date code
Looks like the `500` is now a `405`:

```
$ vault read aws/config/root
Error reading aws/config/root: Error making API request.

URL: GET http://127.0.0.1:8200/v1/aws/config/root
Code: 405. Errors:

* 1 error(s) occurred:

* unsupported operation
```
2016-09-12 15:58:25 -04:00
khanklatt 242105a0ad Correcting typo on "mechanisms" (#1822) 2016-09-01 09:53:20 -04:00
Jeff Mitchell 48eac5434b Bump version 2016-08-22 09:19:13 -04:00
Jeff Mitchell d60caa2a79 Remove old terraform page 2016-08-08 08:26:05 -04:00
Brian Shumate 07dd449e9e Minor grammar edit 2016-07-06 10:02:52 -04:00
Brian Shumate e34146d9d8 Update deploy.html.md
Corrected link to Using PGP, GPG, and Keybase
2016-06-21 12:14:58 -04:00
Jeff Mitchell 33764e85b1 Merge pull request #1324 from hashicorp/sethvargo/doc_gpg
Add a page for step-by-step gpg/keybase
2016-06-03 13:24:57 -04:00
Jeff Mitchell a147c3346c Make some updates to PGP documentation 2016-06-03 13:23:20 -04:00
Sami Rageb 2dba9b180b Fixed & clarified grammar around HCL & JSON
- Fixed the statement that HCL is JSON compatible, it's vice versa
- Added that HCL is a superset of JSON to eliminate any lingering confusion
2016-05-26 20:14:59 -05:00
Francis Chuang ae1d5a8fea Minor grammar fix. 2016-05-19 17:01:30 +10:00
vishalnayak 5c336297ad Provide clarity for output statements of idempotent calls. 2016-04-14 15:46:45 +00:00
vishalnayak b7178846c1 Clarify token-revoke operation 2016-04-14 15:34:01 +00:00
Seth Vargo 54c414abb2
Clarify delete operation
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.
2016-04-14 10:38:10 +01:00
Seth Vargo 2926be9ca7 Add a page for step-by-step gpg/keybase 2016-04-12 21:44:07 +01:00
Jeff Mitchell 0f923d8da5 Merge pull request #1301 from gliptak/patch-3
Update vault read output
2016-04-06 11:26:55 -04:00
Gábor Lipták fa08142921 Update token-create/auth output 2016-04-06 11:14:27 -04:00
Gábor Lipták b2f4d95c27 Update toke-create output 2016-04-06 10:24:19 -04:00
Gábor Lipták f0d3f49601 Update vault read output 2016-04-06 09:13:39 -04:00
Jang-Soo "Bruce" Lee 36d22a0c8d Update consul.html.md 2016-03-30 09:57:14 -04:00