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

Expose simplified 'external' lock reason enum state over REST interface

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Kohn Release
    • None
    • NCMP
    • None

      Although internal we might need more enum values for 'LOCKED_MISBEHAVING' we dont want/need to expose such value to the external clients (and impacting those clients with future new states)

      The simplest approach is in the REST layer to map the (internal) current cm-handle state to a new Rest(?)CmHandleState (open to better name suggestions!)

       Want Now:

      Internal Lock Reason External Lock Reason
      LOCKED_MODULE_SYNC_FAILED LOCKED_MISBEHAVING

      Future?:

      Internal Lock Reason External Lock Reason
      LOCKED_MISBEHAVING LOCKED_MISBEHAVING
      LOCKED_MODULE_SYNC_FAILED LOCKED_MISBEHAVING
      LOCKED_????? LOCKED_MISBEHAVING
      LOCKED_UPGRADING LOCKED_UPGRADING
      LOCKED_OTHER LOCKED_OTHER

      THis user story is to implement such a map in the NCMP Rest Layer

      A/C:
      If module sync fails see LOCKED_MODULE_SYNC_FAILED in db LOCKED_MISBEHAVING in payload
      Are enums documented? Document in openapi description of LOCKED_MISBEHAVING enum
      Only have LOCKED_MODULE_SYNC_FAILED

      Out of scope:
      Service layer not altered

       

            lukegleeson lukegleeson
            ToineSiebelink Toine Siebelink
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: