doc/workflow: YANG is a hard requirement

The text didn't reflect the YANG requirement decision yet.

Signed-off-by: David Lamparter <equinox@opensourcerouting.org>

diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst
index 526f40e3e7e8d2b0385b3fa1ec07d53f5b0017a7..dae175a732da418221bff5ee0a4facf854c190fa 100644 (file)
--- a/doc/developer/workflow.rst
+++ b/doc/developer/workflow.rst
@@ -898,8 +898,15 @@ preference, these are:
 
    This is the preferred way for all FRR knobs.  Not all daemons and features
    are fully YANGified yet, so in some cases new features cannot rely on a
-   YANG interface.  However, if a new feature/PR *can* implement a YANG
-   interface, it probably *should*.
+   YANG interface.  If a daemon already implements a YANG interface (even
+   partial), new CLI options must be implemented through a YANG model.
+
+   .. warning::
+
+      Unlike everything else in this section being guidelines with some slack,
+      implementing and using a YANG interface for new CLI options in (even
+      partially!) YANGified daemons is a hard requirement.
+
 
 -  at configuration/runtime, through the CLI.