From 25e7652449238f638fd25e2c8d52e9e17c8ada00 Mon Sep 17 00:00:00 2001 From: Daniel Kimsey Date: Mon, 21 Sep 2020 11:32:10 -0500 Subject: [PATCH] Clarify consul maint enable/disable scope (#8615) Try to make it more clear to an operator that toggling off a node-level maintenance is independent of toggling service level maintenance. --- website/pages/commands/maint.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/website/pages/commands/maint.mdx b/website/pages/commands/maint.mdx index f260d19b3f..9a2cfa84cd 100644 --- a/website/pages/commands/maint.mdx +++ b/website/pages/commands/maint.mdx @@ -30,11 +30,13 @@ Usage: `consul maint [options]` #### Command Options -- `-enable` - Enable maintenance mode on all services on a node. If - combined with the `-service` flag, we operate on a specific service ID. +- `-enable` - Enable node-wide maintenance mode flag. If combined with the + `-service` flag, we operate on a specific service ID instead. Node and + service maintenance flags are independent. -- `-disable` - Disable maintenance mode on all services on a node. If - combined with the `-service` flag, we operate on a specific service ID. +- `-disable` - Disable the node-wide maintenance flag. If combined with the + `-service` flag, we operate on a specific service ID instead. Node and + service maintenance flags are independent. - `-reason` - An optional reason for placing the service into maintenance mode. If provided, this reason will be visible in the newly-