CM Handle Registration:

http://localhost:8080/ncmpInventory/v1/ch

{
"dmiPlugin": "http://localhost:8082",
"createdCmHandles": [
{
"cmHandle": "Bookstore",
"cmHandleProperties": {
"Bookstore": "library"
},
"publicCmHandleProperties": {
"Book": "Harry Potter",
"Author": "JK Rowling"
}
}
]
} 

Open Questions 

1. During de-registration should we require to remove the operational data from the DB (already synced data)
   Assume so but double check with kieranmccarthy 
2. Do we need a new API for de-registration of CM-handle?
   Registration endpoint allows for 'removedCmHandles' start looking at code form here: org.onap.cps.ncmp.api.impl.NetworkCmProxyDataServiceImpl#parseAndRemoveCmHandlesInDmiRegistration
3. As part of this call, should we remove the CMhandle state from DB?
   NCM-registry data wil be deleted (already done current code) so 'state' no longer exists
4. Add event that state changes to 'DELETING' at the start of above method (or caller)
5. what event(s) to send when delete is finished
   1. State changes to 'DELETED' (is not really happening because we have no stat no more) Check if this is really needed with kieranmccarthy 
   2. cm-handle 'deleted' event as (will) documented here https://wiki.onap.org/display/DW/CPS-1104+Agree+LCM+Event+schemas
6. WIll assume delete request wil not be sent during module/data sync (edge case for later or bug)

A/C

1. Demo deletion of a fully synced (modules and data) cm handle
2. Demonstrate event(s) see open issue #5.1 are sent
3. Demonstrate all data is been removes (use SQL client)