Add support to list child pipelines in project
What does this MR do and why?
Currently we do not support retrieving child pipelines of a project via the API or GraphQL. This can lead to an odd situation, that if the parent pipeline was deleted, one cannot iterate through the child pipelines.
We already return child pipelines if the (undocumented) iids
parameter
is set. By following similar logic, we can just show child pipelines if
the user explicitly filters source=parent_pipeline
which used to
always return an empty list.
Changelog: added
Related to #39503
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Before | After |
---|---|
Screen_Recording_2024-04-17_at_14.47.39 | Screen_Recording_2024-04-17_at_14.48.48 |
Note: The frontend was just the quickest way for me to show it, personally I am more interested that this now works in GraphQL / API.
How to set up and validate locally
- Create a project with child pipelines
- Filter by
source=parent_pipeline