Update DG to Vault 1.0 (#5855)

* Update DG to Vault 1.0

* as per comments  - chrishoffman

* Removed stray bracket and added quotes

* updated as per conversations with Dan
This commit is contained in:
Iain Gray 2019-01-03 15:10:37 +00:00 committed by Chris Hoffman
parent 93955ec98e
commit fe9f34dd2c

View File

@ -6,7 +6,7 @@ description: |-
This deployment guide covers the steps required to install and
configure a single HashiCorp Vault cluster as defined in the
Vault Reference Architecture
product_version: 0.11
product_version: 1.0
---
# Vault Deployment Guide
@ -264,6 +264,20 @@ The `telemetry` stanza specifies various configurations for Vault to publish met
If you decide to configure Vault to publish telemtery data, you should review the [telemetry configuration section](/docs/configuration/telemetry.html) of our documentation.
### High Availability Parameters
The `api_addr` parameter configures the API address used in high availability scenarios, when client redirection is used instead of request forwarding. Client redirection is the fallback method used when request forwarding is turned off or there is an error performing the forwarding. As such, a redirect address is always required for all HA setups.
This parameter value defaults to the `address` specified in the `listener` stanza, but Vault will log a `[WARN]` message if it is not explicitly configured.
Add the below configuration to the Vault configuration file:
```hcl
api_addr = "{{ full URL to Vault API endpoint }}"
```
[More information about high availability configuration](/docs/configuration/#high-availability-parameters).
### Vault UI
Vault features a web-based user interface, allowing you to easily create, read, update, and delete secrets, authenticate, unseal, and more using a graphical user interface, rather than the CLI or API.