mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-13 08:36:45 +02:00
Code Issues Projects Releases Wiki Activity

Fix docs typos (#5158)

Browse Source
This commit is contained in:
Jim Kalafut 2018-08-22 15:26:48 -07:00 committed by Chris Hoffman
parent 9cb81352dd
commit fb2d2de66b
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/guides/operations/vault-ha-consul.html.md
View File

@ -127,7 +127,7 @@ this guide would be `10.1.42.101`, `10.1.42.102`, and `10.1.42.103` respectively
Note that the web user interface is enabled (`"ui": true`), and Consul will be
logging at DEBBUG level to the system log (`"log_level": "DEBUG"`). For the
logging at DEBUG level to the system log (`"log_level": "DEBUG"`). For the
purpose of this guide, the **`acl_enforce_version_8`** is set to `false` so that
we do not need to be concerned with ACLs in this guide. However, you would want
to enable ACLs in a production environment and follow the [Consul ACL Guide](https://www.consul.io/docs/guides/acl.html#acl-agent-master-token) for
@ -489,7 +489,7 @@ We're setting the following parameters for our `tcp` listener:
- `cluster_address` (string: "127.0.0.1:8201") – Specifies the address to bind to for cluster server-to-server requests. This defaults to one port higher than the value of address. This does not usually need to be set, but can be useful in case Vault servers are isolated from each other in such a way that they need to hop through a TCP load balancer or some other scheme in order to talk.
This configuration allows for listening on all interfaces (such that a Vault
command against the loopback address would succeed, for example). Specifical
command against the loopback address would succeed, for example).
We're also explicitly setting Vault's [HA parameters](/docs/configuration/index.html#high-availability-parameters) (`api_addr` and `cluster_addr`). Often, it's not necessary to configure these two parameters when using Consul as Vault's storage backend, as Consul will attempt to automatically discover and advertise the address of the active Vault node. However, certain cluster configurations might require them to be explicitly set (accesing Vault through a load balancer, for example).