From 685838ea0efe6ee68c11f40d5132e8b0a086c2b7 Mon Sep 17 00:00:00 2001 From: Matt Keeler Date: Tue, 26 Jun 2018 15:09:14 -0400 Subject: [PATCH] Fix layout issue with discovery_max_stale It was indented when it shouldn't have been. --- website/source/docs/agent/options.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/agent/options.html.md b/website/source/docs/agent/options.html.md index d2ba21f42..2078fc68d 100644 --- a/website/source/docs/agent/options.html.md +++ b/website/source/docs/agent/options.html.md @@ -752,7 +752,7 @@ Consul will not enable TLS for the HTTP API unless the `https` port has been ass to the Consul raft log in environments where health checks have volatile output like timestamps, process ids, ... - * `discovery_max_stale` - Enables +* `discovery_max_stale` - Enables stale requests for all service discovery HTTP endpoints. This is equivalent to the [`max_stale`](#max_stale) configuration for DNS requests. If this value is zero (default), all service discovery HTTP endpoints are forwarded to the leader. If this value is greater than zero, any Consul server @@ -1360,4 +1360,4 @@ items which are reloaded include: * Node Metadata * Metric Prefix Filter * Discard Check Output -* RPC rate limiting \ No newline at end of file +* RPC rate limiting