-
Task
-
Resolution: Won't Do
-
Major
-
None
-
None
-
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
- Explain for example why/if we need the link in the resource response
- how to retrieve those information (API endpoints)
- pros and cons to use one endpoint over another one if any
- if not possible to retrieve via API endpoints, what are the alternatives