Bug ID 689262: [REST] Policy Diff: canMerged* fields should be enum and not boolean

Last Modified: Jul 12, 2023

Affected Product(s):
BIG-IP ASM(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Fixed In:
14.0.0

Opened: Oct 18, 2017

Severity: 3-Major

Symptoms

canMergeFirstToSecond and canMergeSecondToFirst fields under policy-diff/<id>/differences represent true or false while it should represent the following: - merge-allowed - merge-not-allowed - merge-by-details

Impact

REST display inaccurate data for these fields.

Conditions

Create policy diff with an item that contains inherited and non-inherited values.

Workaround

Review details field that contain the following for each diff item detail: canMergeFirstToSecond/canMergeSecondToFirst

Fix Information

This release fixes the values for canMergeFirstToSecond/canMergeSecondToFirst fields.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips