From abc3643057b31c46fc9ff15346fac7aaa7011bb9 Mon Sep 17 00:00:00 2001 From: Lucy Davinhart Date: Thu, 29 Nov 2018 17:57:30 +0000 Subject: [PATCH] Document /sys/health?perfstandbyok (#5870) * 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: https://github.com/hashicorp/vault/commit/e5aaf80764941d130e6a439f801502bfbc4ee565 * Update health.html.md Slight tweak to wording for perfstandbyok --- website/source/api/system/health.html.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/website/source/api/system/health.html.md b/website/source/api/system/health.html.md index b28fbdd258..ece3ba8ab7 100644 --- a/website/source/api/system/health.html.md +++ b/website/source/api/system/health.html.md @@ -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.