rename vault id to lease id all over

This commit is contained in:
Mitchell Hashimoto 2015-04-10 20:35:14 -07:00
parent 3c9b4182cb
commit 48205d166b
4 changed files with 6 additions and 6 deletions

View File

@ -148,5 +148,5 @@ the "name" parameter. For example, if this backend is mounted at "aws",
then "aws/deploy" would generate access keys for the "deploy" policy.
The access keys will have a lease associated with them. The access keys
can be revoked by using the Vault ID.
can be revoked by using the lease ID.
`

View File

@ -58,13 +58,13 @@ func (c *RevokeCommand) Help() string {
helpText := `
Usage: vault revoke [options] id
Revoke a secret by its Vault ID.
Revoke a secret by its lease ID.
This command revokes a secret by its Vault ID that was returned
This command revokes a secret by its lease ID that was returned
with it. Once the key is revoked, it is no longer valid.
With the -prefix flag, the revoke is done by prefix: any secret prefixed
with the given partial ID is revoked. Vault IDs are structured in such
with the given partial ID is revoked. Lease IDs are structured in such
a way to make revocation of prefixes useful.
General Options:

View File

@ -138,7 +138,7 @@ Let's complete the loop and revoke this secret now, purging it from
existence. Once the secret is revoked, the access keys will no longer
work.
To revoke the secret, use `vault revoke` with the vault ID that was
To revoke the secret, use `vault revoke` with the lease ID that was
outputted from `vault read` when you ran it:
```

View File

@ -94,7 +94,7 @@ the "name" parameter. For example, if this backend is mounted at "aws",
then "aws/deploy" would generate access keys for the "deploy" policy.
The access keys will have a lease associated with them. The access keys
can be revoked by using the Vault ID.
can be revoked by using the lease ID.
```
Within a path, we're given the parameters that this path requires.