docs: added information about a conflict when using auto_config and auto_encrypt

This commit is contained in:
Karl Cardenas 2021-08-25 21:25:18 -07:00
parent bb9188bb45
commit 8eab6b65b7
No known key found for this signature in database
GPG Key ID: 0AC61D76B41F1EDC
1 changed files with 12 additions and 6 deletions

View File

@ -547,12 +547,12 @@ definitions support being updated during a reload.
"server": true,
"watches": [
{
"type": "checks",
"handler": "/usr/bin/health-check-handler.sh"
"type": "checks",
"handler": "/usr/bin/health-check-handler.sh"
}
],
"telemetry": {
"statsite_address": "127.0.0.1:2180"
"statsite_address": "127.0.0.1:2180"
}
}
```
@ -609,8 +609,8 @@ Valid time units are 'ns', 'us' (or 'µs'), 'ms', 's', 'm', 'h'."
In "deny" mode, ACLs are an allowlist: any operation not specifically
allowed is blocked. **Note**: this will not take effect until you've enabled ACLs.
- `enable_key_list_policy` ((#acl_enable_key_list_policy)) - Boolean value, defaults to false.
When true, the `list` permission will be required on the prefix being recursively read from the KV store.
- `enable_key_list_policy` ((#acl_enable_key_list_policy)) - Boolean value, defaults to false.
When true, the `list` permission will be required on the prefix being recursively read from the KV store.
Regardless of being enabled, the full set of KV entries under the prefix will be filtered
to remove any entries that the request's ACL token does not grant at least read
permissions. This option is only available in Consul 1.0 and newer.
@ -1051,6 +1051,9 @@ Valid time units are 'ns', 'us' (or 'µs'), 'ms', 's', 'm', 'h'."
- `segment` <EnterpriseAlert inline /> - The network segment name the client is requesting.
~> **Warning:** Enabling `auto_config` conflicts with the `auto_encrypt.tls` feature.
Only one option may be specified.
- `auto_encrypt` This object allows setting options for the `auto_encrypt` feature.
The following sub-keys are available:
@ -1087,6 +1090,9 @@ Valid time units are 'ns', 'us' (or 'µs'), 'ms', 's', 'm', 'h'."
the certificates requested by `auto_encrypt` from the server have these `ip_san`
set as IP SAN.
~> **Warning:** Enabling `auto_encrypt.tls` conflicts with the `auto_config` feature.
Only one option may be specified.
- `bootstrap` Equivalent to the [`-bootstrap` command-line flag](#_bootstrap).
- `bootstrap_expect` Equivalent to the [`-bootstrap-expect` command-line flag](#_bootstrap_expect).
@ -1605,7 +1611,7 @@ bind_addr = "{{ GetPrivateInterfaces | include \"network\" \"10.0.0.0/8\" | attr
- `use_cache` ((#http_config_use_cache)) Defaults to true. If disabled, the agent won't be using [agent caching](/api/features/caching) to answer the request. Even when the url parameter is provided.
- `max_header_bytes` This setting controls the maximum number of bytes the consul http server will read parsing the request header's keys and values, including the request line. It does not limit the size of the request body. If zero, or negative, http.DefaultMaxHeaderBytes is used, which equates to 1 Megabyte.
- `max_header_bytes` This setting controls the maximum number of bytes the consul http server will read parsing the request header's keys and values, including the request line. It does not limit the size of the request body. If zero, or negative, http.DefaultMaxHeaderBytes is used, which equates to 1 Megabyte.
- `leave_on_terminate` If enabled, when the agent receives a TERM signal, it will send a `Leave` message to the rest of the cluster and gracefully leave. The default behavior for this feature varies based on whether or not the agent is running as a client or a server (prior to Consul 0.7 the default value was unconditionally set to `false`). On agents in client-mode, this defaults to `true` and for agents in server-mode, this defaults to `false`.