Uploaded image for project: 'Configuration Persistence Service'
  1. Configuration Persistence Service
  2. CPS-1001 Add CPS-E-05 endpoint for 'Read data, NCMP-Operational Datastore'
  3. CPS-1219

handle invalid operations (REST methods) on merged datastore endpoint

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Medium Medium
    • Kohn Release
    • None
    • NCMP

      Other uses cases also covered by these endpoints and they have to be handled separately for backward compatibility reasons

      Existing (separate) URL Endpoints

      1. /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-operational:
        1. get
      2. /v1/ch/{cm-handle}/data/ds/ncmp-datastore:passthrough-running[?topicName,includeDescendant]:
        1. get
        2. post
        3. put
        4. patch
        5. delete

      New approach ONE generic URL

      /v1/ch/{cm-handle}/data/ds/<dataStoreName>?topicName, 

      Datastore get post put patch delete
      passthrough-operational supported No No No No
      passthrough-running supported supported supported supported supported
      operational supported No No No No

      Insert a check at the start of post, put, path, delete for datastores, thrown an exception if it is not 'passtrough-running' -> handle with 400 (bad request)

       

            bmiklos bmiklos
            bmiklos bmiklos
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: