Details
-
Task
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
-
1.0-japan-m9
Description
In Scope
- API needs to change to return a flattened out list with paths at the top level only
- Subfolders should return only their contents (as they do now)
- An option should be allowed to specify that non flattened list is required (but is not the default)
- Should not result in recursing through folders, or load all jobs into memory
- Objects returns should have links/paths that include the folderName/pipelines/subfolderName/pipelines/PipelineName style of naming so the URI can be set and the data loaded
Attachments
Issue Links
- blocks
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
Activity
vpandey ok making it an option is ok for consistency.
On performance, I mean that pagination should not require that the whole set is loaded into memory.
vivek so this is closed - but not sure what we have to do to get a flattened list back out. Could you add an example to the rest api docs? (or is it default behavior?)
jdumaymneale
>An option should be allowed to specify that non flattened list is required (but is not the default)
From the API perspective, it will be more consistent to return non-flattened list by default and returned flattened list via query parameter. Its can also can be expensive call so better serve it with parameter.
>Should not result in recursing through folders, or load all jobs into memory
Any collection call is expensive, client should use pagination to limit how many items are returned in per call.