There is a need to check a filter for configuration changes before putting it in production. The 'Compare filters' report does not do the job, because
- It does not compare attribute values but even if its customised to do so:
- It can be run only within one server, which is either too late or not relevant. If the method extension is imported with the filter, there will be no changes detected because the configuration of the target server will be altered already. If method changes are not applied then the role of the filter as transport mechanism for configuration changes will not be used.
One of the solutions can be to compare two filters form two different servers. Any ideas how to do so? Or alternative ways to detect configuration changes within filtered area?