scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-11-01 02:57:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix minor spelling mistake (#4548)

Browse Source
This commit is contained in:
Tyler Marshall
2018-05-10 16:42:01 -04:00
committed by Jim Kalafut
parent 5f342b4aa0
commit 9e059e65e9
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
CHANGELOG.md
View File

@@ -706,7 +706,7 @@ DEPRECATIONS/CHANGES:
* SSH role list changes: When listing roles from the `ssh` backend via the API, * SSH role list changes: When listing roles from the `ssh` backend via the API,
the response data will additionally return a `key_info` map that will contain the response data will additionally return a `key_info` map that will contain
a map of each key with a corresponding object containing the `key_type`. a map of each key with a corresponding object containing the `key_type`.
* More granularity in audit logs: Audit request and response entires are still * More granularity in audit logs: Audit request and response entries are still
in RFC3339 format but now have a granularity of nanoseconds. in RFC3339 format but now have a granularity of nanoseconds.
* High availability related values have been moved out of the `storage` and * High availability related values have been moved out of the `storage` and
`ha_storage` stanzas, and into the top-level configuration. `redirect_addr` `ha_storage` stanzas, and into the top-level configuration. `redirect_addr`

2
command/operator_init.go
View File

@@ -125,7 +125,7 @@ func (c *OperatorInitCommand) Flags() *FlagSets {
"public GPG keys OR a comma-separated list of Keybase usernames using " + "public GPG keys OR a comma-separated list of Keybase usernames using " +
"the format \"keybase:<username>\". When supplied, the generated " + "the format \"keybase:<username>\". When supplied, the generated " +
"unseal keys will be encrypted and base64-encoded in the order " + "unseal keys will be encrypted and base64-encoded in the order " +
"specified in this list. The number of entires must match -key-shares, " + "specified in this list. The number of entries must match -key-shares, " +
"unless -store-shares are used.", "unless -store-shares are used.",
}) })

2
website/source/docs/commands/operator/init.html.md
View File

@@ -74,7 +74,7 @@ flags](/docs/commands/index.html) included on all commands.
containing public GPG keys OR a comma-separated list of Keybase usernames containing public GPG keys OR a comma-separated list of Keybase usernames
using the format "keybase:<username>". When supplied, the generated unseal using the format "keybase:<username>". When supplied, the generated unseal
keys will be encrypted and base64-encoded in the order specified in this list. keys will be encrypted and base64-encoded in the order specified in this list.
The number of entires must match -key-shares, unless -store-shares are used. The number of entries must match -key-shares, unless -store-shares are used.
- `-root-token-pgp-key` `(string: "")` - Path to a file on disk containing a - `-root-token-pgp-key` `(string: "")` - Path to a file on disk containing a
binary or base64-encoded public GPG key. This can also be specified as a binary or base64-encoded public GPG key. This can also be specified as a

2
website/source/guides/upgrading/upgrade-to-0.9.0.html.md
View File

@@ -115,7 +115,7 @@ corresponding object containing the `key_type`.
### More granularity in audit logs (In 0.9) ### More granularity in audit logs (In 0.9)
Audit request and response entires are still in RFC3339 format but now have a Audit request and response entries are still in RFC3339 format but now have a
granularity of nanoseconds. granularity of nanoseconds.
[generate-root]: https://www.vaultproject.io/api/secret/pki/index.html#generate-root [generate-root]: https://www.vaultproject.io/api/secret/pki/index.html#generate-root