Introduction of assigned licenses breaks existing group-based licensing

[anpiskai]

An existing configuration with groups did not have the AssignedLicenses parameter specified and as a result, when it ran the new build of DSC, it unlicensed the groups. This would make sense if the assignedLicenses was specified and configured to be null to avoid configuration drift, however the code shouldn't touch the AssignedLicenses on a group if that attribute is not specified. (Same for the Members attribute).

[andikrueger]

DSC will configure the parameter specified. If you do not wish to configure this parameter, please remove it completely within you configuration.

Pseudo Code that will control optional parameter

ResourceName DisplayName {
   KezParameter = "This is the Key"
   OptionalParameter = "Configure Something"
}

Pseudo Code that will not change the optional parameter

ResourceName DisplayName {
   KezParameter = "This is the Key"
}

[anpiskai]

Neither is present in the attributes specified on the resource.

[andikrueger]

Thanks for confirming. This need to be investigated.