Backend: Add filtering/better routes for Pipelines/DataInstances
Problem to Solve
Describe the desired state of the system in the style of: “As a (User / Manager / Admin / Guest) I want to be able to do x”
For many use cases we need to fetch "datainstances"/"datasets", or visualisationpipelines.
Right now, we have a general pipeline endpoint: https://mlreef.gitlab.io/backend/develop/#_get_pipelines
We need do add a function, that we can a) filter or b) specify the value via the url
e.g.:
- /project/:id/pipelines?type=DATA /project/:id/pipelines?type=DATA,VISUALISATION (quite mighty)
- or /project/:id/datainstances/:pid and /project/:id/visualisation-pipelines
- /project/:id/pipelines/:pid can work in any case, and already does
@diegovinie do you prefer a dynamic filter or type-fixed urls?
-> list some "job", is this gitlab pipeline info, or our pipelines?
https://mlreef.com/:namespace/:project_slug/-/visualization/:visualization_ID
-> retrieve a certain VisualisationPipeline from a DataProject or retrieve VisualisationProcessor from a CodeProject, what is that?
Technical Solution
Add technical implementation details and the results of the ticket's discussion here.