Bug ID 2217925: Comments are not supported in DCP/JSON Policy Block

Last Modified: Feb 19, 2026

Affected Product(s):
BIG-IP LTM, SSLO(all modules)

Known Affected Versions:
17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1

Opened: Jan 28, 2026

Severity: 3-Major

Symptoms

In the Policy format, there can be multiple policies in one document, separated by `---`. The DCP Policy Editor exclusively reads from and writes to a specific one of these blocks called the "Regulus Policy" which is a JSON object with one top-level field "RegulusPolicy". Since this is parsed using a JSON parser, if comments are added to this block, then the block is no longer valid JSON, therefore it is ignored and the Regulus Policy is reinitialized to the default (empty) values.

Impact

Should not impact end users during normal operation. Only occurs during unsupported usage.

Conditions

It is not possible to insert comments during normal usage of the policy editor, this only happens if the policy was manually edited outside of the GUI editor, which is not supported.

Workaround

Don't use comments in the JSON block. Comments in the YAML blocks are supported and do not trigger this bug.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips