Details
-
Bug
-
Status: Closed
-
Medium
-
Resolution: Done
-
Istanbul Release
-
None
Description
The registration process of a CM-Handle can have three potential steps
- CM-Handle Creation
- CM-Handle update
- CM-Handle removal
Currently in the code it is handled within this order.
If the process fails at any of these steps, for any reason, the succeeding step will not process.
Eg. If the creation step fails, the CM-Handle update step will not execute, and if the update step fails, the CM-Handle removal step will not execute.
There is also currently no way for the client to tell which step fails within the process
Consider
- Repsonscode 206 v 200 v error code
- Include failed or succeeded (need to discuss with Stakeholder)
Attachments
Issue Links
- is duplicated by
-
CPS-628 Spike: Robustness for partial results
-
- Closed
-
- relates to
-
CPS-628 Spike: Robustness for partial results
-
- Closed
-
-
CPS-922 CSIT Tests for NCMP-DMI Plugin - Scenarios
-
- Closed
-
-
CPS-927 Create cm handle from NCMP Inventory returns Server Error caused by LogFormatUtils error
-
- Closed
-
-
CPS-928 Create cm handle from NCMP Inventory returns Server Error when cm handle already exists
-
- Closed
-