For configuration updates, including COMMON-SYSPROPS type, the currently/commonly supported behavior is a ‘complete update’:
- get full copy locally
- modify local copy (add, remove, update properties)
- submit modified copy
This is what IS plugin supports for COMMON-SYSPROPS.
If you know how the configuration should look like, independently of what it was, you can replace the process with
- have a local ‘target’ copy
- submit it
This process is what composite templates are based on. They set the target configuration state independently from what was there.
Some products/configurations support ‘partial configuration updates’. For example Universal Messaging 9.9 supports COMMON-SYSPROPS type for Realm Properties configuration and you can submit only properties that you’d like to change:
This approach works well for configurations that have known/fixed properties set, e.g. clients cannot add/remove properties, only modify.
This is not the case with IS. If IS COMMON-SYSPROPS supported partial configuration update it would not be possible to remove properties.
Having said this, we’re considering to formalize ‘partial configuration updates’ at some point, though no concrete plans at the moment.