From cd1aa9b426ddc7c9f73ac8fb2868d9c32d215d4e Mon Sep 17 00:00:00 2001 From: Reid Beels Date: Tue, 12 Mar 2019 11:26:40 -0400 Subject: [PATCH] Remove misleading encrypt param documentation (#5452) According to https://www.consul.io/docs/agent/options.html#_encrypt, the `encrypt` param specifies the 16-byte key to use, not the path to a config file containing the key. --- website/source/docs/agent/encryption.html.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/website/source/docs/agent/encryption.html.md b/website/source/docs/agent/encryption.html.md index 8e04348429..9d5a9b0d2e 100644 --- a/website/source/docs/agent/encryption.html.md +++ b/website/source/docs/agent/encryption.html.md @@ -16,8 +16,7 @@ If you are configuring encryption, review this [guide](/docs/guides/agent-encryp ## Gossip Encryption Enabling gossip encryption only requires that you set an encryption key when -starting the Consul agent. The key can be set via the `encrypt` parameter: the -value of this setting is a configuration file containing the encryption key. +starting the Consul agent. The key can be set via the `encrypt` parameter. ~> **WAN Joined Datacenters Note:** If using multiple WAN joined datacenters, be sure to use _the same encryption key_ in all datacenters.