Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-896

CM Handle Registration Process only partially completes when exception is thrown

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Kohn Release
    • Istanbul Release
    • CPS-Core, NCMP
    • None

      The registration process of a CM-Handle can have three potential steps

      1. CM-Handle Creation
      2. CM-Handle update
      3. 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)

       

        1.
        		 Fix the cmhandle registration request example in the openapi.yaml Sub-task Closed renukumari
        2.
        		 Send Response for the updateCMHandle operations Sub-task Closed renukumari
        3.
        		 Send Response for the remove CMHandle operations Sub-task Closed renukumari
        4.
        		 Update rest interface and controller layer Sub-task Closed renukumari
        5.
        		 Send Response for the create CMHandle operations Sub-task Closed renukumari
        6.
        		 Update Read the docs with expected error-codes Sub-task Closed renukumari

            renukumari renukumari
            dylanb95est dylanb95est
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: