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

Create OAS for Account listing page

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • System
    • 5
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

      Account listing page needs data from Porta, the following would be needed:

      Request Query params (AuthZ/AuthN would be added in a different ticket when we agreed on a solution):

      • page
      • per_page
      • state

      Response:

      • id
      • group/org name (*link to resource)
      • admin name
      • created / updated_at
      • apps amount (*link to resource)
      • state

      Relevant issues:
      Design: https://issues.redhat.com/browse/THREESCALE-4725
      Component: https://issues.redhat.com/browse/THREESCALE-4732
      Integration alternatives Porta API / New endpoint: https://issues.redhat.com/browse/THREESCALE-4733

      Please fill in different implementations

      • Propose at least 2 implementation of this OAS 3.0 spec
      1. Explain for example why/if we need the link in the resource response
      2. how to retrieve those information (API endpoints)
      3. pros and cons to use one endpoint over another one if any
      4. if not possible to retrieve via API endpoints, what are the alternatives

              Unassigned Unassigned
              dcesare Didier Di Cesare (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: