Rudder

Here we add some new targets that allow composition of targets.

• TargetUnion, which should be transform to union of all set of Nodes from those targets
• TargetIntersection, to be transformed in the interstion of add set of Nodes from those targets

and another target (targetExclusion) to select groups that we want the rule to be applied and groups that we clearly don't want.
This should be transformed into the set of Nodes included targets and remove Nodes from excluded ones.

before 2.10, When a Rule applies more than one rule targets, Rudder considers them as being an union of all those targets, and therefore we decided that when you will modify a Rule that has multiple targets in 2.10, those targets will be transformed into one target that would include an union of all of the targets.

ie: if your Rule applies to groups G1, G2, G3, when you will access that Rule via Rudder webUI it will transform it into one and only target that include the three groups and does not exclude any groups.

Those three new targets will be represented as json in the ldap, so you can directly use it the API.

Target composition (Union/Intersection) are represented like this:

{ "targets" : [List of targets], "kind" : "Union or Intersection" }

The composite Target that include and exclude targets will be reprsented like this:

{ "include" : a target composition , "kind" : a target composition }

ie: the case from previous update would be represented like that:

{ "include" : { "targets" : [ "G1", "G2", "G3" ] , "kind" : "union" }, "exclude" : { "targets" : [ ] , "kind" : "union" } }

Oops, an error appeared on last update (example is correct though)

target composition will be represented like that:

{ "include" : a target composition , "exclude" : a target composition }

Applied in changeset 170236e147a4fe5ada7fde94c965b735290120ea.