Rudder

The goal of that feature is to allows to merge a change request on a Directive's parameter even if some non conflicting parameter changed in that directive since the Change Request creation.

Considering the following example (iteration number is noted with iter="n" for clarity even if that is not in the xml)

<section name="sections">
      <section name="s" iter="0">
        <var name="p1">v1</var>
        <var name="p2">v2</var>
      </section>
      <section name="s" iter="1">
        <var name="p1">v3</var>
        <var name="p2">v4</var>
      </section>
    </section>

The broad logic for that feature is:
- build a FQDN (Full Qualified (Directory) Name) of each parameter
- we consider both section and section iteration in a multivalued section, so that in our example, fqdn for p2 in section "s" iter 1 is "sections.s.1.p1"
- sections.x.y.0.z.varName is the same as sections.x.y.z.varName
- only look for actually modified vars given their fqdn
- check for modification of these parameters between change request creation time and now,
- finally, look for uncompatible values for fqdn modified in both case