CmHandles could change their cm additional properties.

NCMP can be informed of this using the existing (registration) API call on NCMP (#1 in https://wiki.onap.org/display/DW/CPS-390+Spike%3A+Define+and+Agree+DMI+Plugin+REST+Interface#CPS390Spike:DefineandAgreeDMIPluginRESTInterface-DMIInventory,Model&DataSyncAPI) 

 For this user story the payload labeled "updatedcmhandles" needs to be implemented. ie. any entries in this need to be updated in the registry

If an entry in "updatedcmhandles"  does not exist we can probably silently ignore and handles it as 'new' (to be agreed)

A/C
Update the schema in the yaml file to include an operation to indicate it is an update operation
Add a new method to ncmp service Interface
Call method in the cps java API updateNodeLeaves
Persist cm handle changes in the db