luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: clarify acl down policy

This commit is contained in:
Daniel Nephin 2021-09-23 17:11:10 -04:00
parent 30fe14eed3
commit 52ecd0d107
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/agent/options.mdx
View File

@ -596,8 +596,10 @@ Valid time units are 'ns', 'us' (or 'µs'), 'ms', 's', 'm', 'h'."
token cannot be read from the [`primary_datacenter`](#primary_datacenter) or token cannot be read from the [`primary_datacenter`](#primary_datacenter) or
leader node, the down policy is applied. In "allow" mode, all actions are permitted, leader node, the down policy is applied. In "allow" mode, all actions are permitted,
"deny" restricts all operations, and "extend-cache" allows any cached objects "deny" restricts all operations, and "extend-cache" allows any cached objects
to be used, ignoring their TTL values. If a non-cached ACL is used, "extend-cache" to be used, ignoring the expiry time of the cached entry. If the request uses an
acts like "deny". The value "async-cache" acts the same way as "extend-cache" ACL that is not in the cache, "extend-cache" falls back to the behaviour of
`default_policy`.
The value "async-cache" acts the same way as "extend-cache"
but performs updates asynchronously when ACL is present but its TTL is expired, but performs updates asynchronously when ACL is present but its TTL is expired,
thus, if latency is bad between the primary and secondary datacenters, latency thus, if latency is bad between the primary and secondary datacenters, latency
of operations is not impacted. of operations is not impacted.