Skip to content

Converted PriorityMembers and PriorityZone to Lists#414

Open
computeythings wants to merge 1 commit intofortinetdev:mainfrom
computeythings:fix-priority-member-zone-order
Open

Converted PriorityMembers and PriorityZone to Lists#414
computeythings wants to merge 1 commit intofortinetdev:mainfrom
computeythings:fix-priority-member-zone-order

Conversation

@computeythings
Copy link
Copy Markdown

Summary

Converted the schema type of the system.sdwan.service.priority_members and system.sdwan.service.priority_zone to lists to ensure deterministic order and detect changes in that order.

Problem

Current resources were configured as Sets which ignored order and would change priority order when pushed to the default sorted order.

Solution

Changed schema to TypeList from TypeSet.
Modified the respective flatten functions to detect tf_exists on list size and compare value based on list index.
Removed dynamic_sort_subtable on the flatten functions - these should not be auto-sorted.

Testing

Tested on live devices. Confirmed drift is detected from live config and re-ordering values is correctly registered as a change.

Notes

Tested on FortiGate 400F FortiOS v7.4.7
Fixes #356

@computeythings computeythings force-pushed the fix-priority-member-zone-order branch from 79966ab to 94ebd43 Compare March 6, 2026 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SD-WAN service priority_members order

1 participant