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

Document /sys/health?perfstandbyok (#5870)

Browse Source 
* Document /sys/health?perfstandbyok

Discovered that in Vault Enterprise 0.11.5, `/sys/health?standbyok` returns a 473 status for performance standby nodes, compared to a 200 for standard standby nodes.

Turns out there was an additional `perfstandbyok` option added, here:
e5aaf80764

* Update health.html.md

Slight tweak to wording for perfstandbyok
This commit is contained in:
Lucy Davinhart 2018-11-29 17:57:30 +00:00 committed by Brian Kassouf
parent 8dd46cf04e
commit abc3643057
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/source/api/system/health.html.md
View File

@ -36,7 +36,12 @@ The default status codes are:
- `standbyok` `(bool: false)` – Specifies if being a standby should still return
the active status code instead of the standby status code. This is useful when
Vault is behind a non-configurable load balance that just wants a 200-level
response.
response. This will not apply if the node is a performance standby.
- `perfstandbyok` `(bool: false)` – Specifies if being a performance standby should
still return the active status code instead of the performance standby status code.
This is useful when Vault is behind a non-configurable load balance that just wants
a 200-level response.
- `activecode` `(int: 200)` – Specifies the status code that should be returned
for an active node.