From 3f93e5d9f9305512a95def8cf2aba22cc056420f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0pa=C4=8Dek?= Date: Fri, 1 Jul 2022 14:31:14 +0200 Subject: [PATCH] Remove key_list grammar definition It was used in a single place (inet statement) and it defined it in the text anyway. Let's not clutter the glossary. (cherry picked from commit 818219b36aeea95d1e9646fa967e0de7ddf2b692) --- doc/arm/reference.rst | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index e4aa0a4033..d4e908d5e2 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -313,9 +313,6 @@ file documentation: :ref:`transaction security `. Keys are defined using :namedconf:ref:`key` blocks. - ``key_list`` - A list of one or more :term:`key_id` s, separated by semicolons and ending with a semicolon. - ``tls_id`` A string representing a TLS configuration object, including a key and certificate. @@ -490,7 +487,7 @@ and retrieve non-DNS results from a name server. :any:`keys` The primary authorization mechanism of the command channel is the - :term:`key_list`, which contains a list of :term:`key_id` s. Each + list of :term:`key_id` s. Each listed :namedconf:ref:`key` is authorized to execute commands over the control channel. See :ref:`admin_tools` for information about configuring keys in :iscman:`rndc`.