-
Task
-
Resolution: Won't Do
-
Normal
-
None
-
None
-
None
-
5
-
False
-
None
-
False
-
-
Cost Management OpenAPI spec content is lean and could be improved now that we have more customer usage. We can also improve the maintainability of the OpenAPI spec by subdividing it into smaller pieces.
Link: https://github.com/project-koku/koku/blob/main/docs/specs/openapi.json
Goals:
- Describe API at a high level near the top. Provide a basic tutorial about how to do filtering/grouping.
- Describe the limitations of the API. For example, supported date ranges and limits on grouping
- Improve each API description so that it provides a user-friendly description of the API group and individual APIs
- Responses need descriptions
1.
|
Divide the OpenAPI Spec into smaller chunks | Closed | Unassigned | ||
2.
|
Describe API at a high level near the top. Provide a basic tutorial about how to do filtering/grouping | Closed | Unassigned | ||
3.
|
Describe the limitations of the API. For example, supported date ranges and limits on grouping | Closed | Unassigned | ||
4.
|
Ensure QE automation has a path if the OpenAPI Spec is broken into pieces | Closed | Unassigned | ||
5.
|
Modify API header text | Closed | Unassigned | ||
6.
|
Document "exact" match on get openshift report filter | Closed | Unassigned |