Is your feature request related to a problem? Please describe.
With the update to version 24.7, a new setting Sync compatibility is required as seen in the GUI:
Furthermore, the services to be sync can now be added via multi-select dropdown:
These two changes do influence the xml-config in the following way:
A new element pfsyncversion is introduced which, according to my tests can either have the value 1400 for OPNsense 24.7 or above or 1301 for OPNsense 24.1[.x] or below.
The syncelements are now a comma separated string other than a specific element per option.
Describe the solution you'd like
The system_high_availability_settings module must be version-aware and generate a different XML for version 24.7.
Additional context
Since the current module would break the 24.7 configuration, this changes must be made before adding 24.7 version compatibility.
Is your feature request related to a problem? Please describe. With the update to version 24.7, a new setting
Sync compatibility
is required as seen in the GUI:Furthermore, the services to be sync can now be added via multi-select dropdown:
These two changes do influence the xml-config in the following way:
I want to point out two relevant changes:
pfsyncversion
is introduced which, according to my tests can either have the value1400
forOPNsense 24.7 or above
or1301
for OPNsense 24.1[.x] or below.syncelements
are now a comma separated string other than a specific element per option.Describe the solution you'd like The
system_high_availability_settings
module must be version-aware and generate a different XML for version 24.7.Additional context Since the current module would break the 24.7 configuration, this changes must be made before adding 24.7 version compatibility.