Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-3883

Create JSON versions of existing (undocumented, unsupported) CMS API methods

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • None
    • System
    • None
    • 5
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      In order to enable some exploration of an external CMS tool as part of 3scale-toolbox, we would like to have json versions of the existing XML-only CMS API methods.

      NOTE: These will remain undocumented and unsupported until a decision is made on the path forward. So, it is possible to take some short-cuts when implementing them, which may require re-visiting later to "polish" if we decide to go this path.

      Also, we are discussing documenting our API in OAS 3.0 using apicurio - so providing it's relatively clear how to use these endpoints (for a 3scale developer doing experimentation) there is no need for new API docs for them.

      API Methods required are:

      • list
      • update
      • delete
      • create
        for each of CMS 'templates', 'files' and 'sections'

      Some of the relevant files: (https://github.com/3scale/porta/search?q=%22%2Fadmin%2Fapi%2Fcms%2F%22&unscoped_q=%22%2Fadmin%2Fapi%2Fcms%2F%22)
      Tests

      Rspecs

      Controllers:

              Unassigned Unassigned
              amackenz@redhat.com Andrew Mackenzie
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: