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

DP: Agree and document proposed long-term REST API(s)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • CPS-Core

      Although the PoC will only implement a few of the possible REST API methods it is important to have a good detailed view of the structure and naming of this interface going forward and document it.

      Acceptance Criteria for Proposed REST Interface:

      1. Should follow ONAP or wider best practice
        1. Use swagger to design interface (& generate Open API document)
      2. Discussed and agreed within CPS Team (incl. Tony)
      3. Discussed and agreed with wider community
        1. Share generated HTML document

      Note. any output will remain a 'draft'  (version 0.01 ) and can change as we implement these methods.

      Currently we are considering 3 'separated' REST APIs or 'groups' of methods:

      1. Models (add, list)
      2. Data (CRUD)
      3. Queries

      See also https://wiki.onap.org/pages/viewpage.action?pageId=84655884#HighLevelDesign(PoC)-Interfaces

            niamhcore niamhcore
            ToineSiebelink Toine Siebelink
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: