The do_update parameter is an optional addition to the groups and exclusion_groups dictionaries within the arguments of a JSS recipe. This allows the recipe to specify a computer group to be added to the Targets and Exclusions of a policy, but not to update the smart groups if they already exist. The default behaviour is do_update == True, which is the same as the current behaviour. If <key>do_update</key><false/> is added to a group dictionary, an existing group of the specifying name will not be overwritten/updated.
The use case for this change is that an administrator can automatically provide smart groups via AutoPkg, which can then be altered - most likely, the criteria is changed. More broadly, the idea is that JSSImporter can be used to create a set of production policies for a software title, some of which will change with new software versions, but some will not, and need to have adjustable scope.
The
do_update
parameter is an optional addition to thegroups
andexclusion_groups
dictionaries within the arguments of a JSS recipe. This allows the recipe to specify a computer group to be added to the Targets and Exclusions of a policy, but not to update the smart groups if they already exist. The default behaviour isdo_update == True
, which is the same as the current behaviour. If<key>do_update</key><false/>
is added to a group dictionary, an existing group of the specifying name will not be overwritten/updated.The use case for this change is that an administrator can automatically provide smart groups via AutoPkg, which can then be altered - most likely, the criteria is changed. More broadly, the idea is that JSSImporter can be used to create a set of production policies for a software title, some of which will change with new software versions, but some will not, and need to have adjustable scope.
Example: