DDM: add an activation for each declaration

[roperzh]

Context

From Apple's Documentation

If at least one activation that references a configuration is active, the system applies the policies defined by the configuration.

So we need at least one activation. Note that:

Activations have a many-to-many relationship with configurations: one activation can reference many configurations, and many activations can reference the same configuration.

But we still want to do one activation per declaration because of:

Activations contain a set of configurations that the system applies atomically to the device, such that the system applies all referenced configurations together, or none.

So if each declaration is independent from the others.

Implementation

• After a configuration is uploaded via the UI or the CLI, create a new activation that references it, and it doesn't contain any conditional values (ie: always evaluates to true)

{
  "Identifier": "com.fleet.activation.${identifier}",
  "Payload": {
    "StandardConfigurations": [
      "${configuration_identifier}"
    ]
  },
  "ServerToken": "",
  "Type": "com.apple.activation.simple"
}

• For ServerToken, start with a random UUID, refine if necessary
• Insert this activation in the mdm_apple_declarations table

[georgekarrv]

Hey team! Please add your planning poker estimate with Zenhub @dantecatalfamo @ghernandez345 @gillespi314 @jahzielv @mna @roperzh

[georgekarrv]

declaration configuration activition obliteration

[fleet-release]

Activation per declaration,
Ease and control in the equation.
A breeze through configurations.