[#3855] Applied patch to update ARM

diff --git a/changelog_unreleased/3855-documentation-update-for-user-contexts b/changelog_unreleased/3855-documentation-update-for-user-contexts
new file mode 100644 (file)
index 0000000..1aa3ca3
--- /dev/null
+++ b/changelog_unreleased/3855-documentation-update-for-user-contexts
@@ -0,0 +1,4 @@
+[doc]          tmark
+       Updated list of elements supporting user-context
+       in ARM.
+       (Gitlab #3855)

diff --git a/doc/sphinx/arm/config.rst b/doc/sphinx/arm/config.rst
index bda2d2804dde33cc678424f3320193c4344ed3ab..6d8c42b64821312f45bdbcfad783176741f23735 100644 (file)
--- a/doc/sphinx/arm/config.rst
+++ b/doc/sphinx/arm/config.rst
@@ -187,11 +187,13 @@ The best way to avoid this problem is simply to abandon JSON comments and
 use user context.
 
 Kea supports user contexts at the following levels: global scope,
-interfaces configuration, shared networks,
-subnets, client classes, option data and definitions, host
-reservations, control socket, DHCP-DDNS, loggers, leases, and server ID. These
-are supported in both DHCPv4 and DHCPv6, with the exception of server ID,
-which is DHCPv6 only.
+interfaces configuration, multi-threading, shared networks, subnets,
+client classes, option data and definitions, pools, prefix delegation pools,
+host reservations, control socket, HTTP header, authentication, clients,
+queue control, DHCP-DDNS, loggers, leases, and server ID. These are supported
+in both DHCPv4 and DHCPv6, with the exception of prefix delegation pools and
+server ID, which are DHCPv6 only.
+
 
 User context can be added and edited in structures supported by commands.