GraphQL API: Add associatedProjects field to CiRunner

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Description

In #349452 (closed) we added a projects field to CiRunner in our GraphQL API to fetch the projects that a runner is assigned to.

We have since segregated the project owns the runner (ownerProject), as this project cannot be modified. We implemented this into our runner mutations in RunnerUpdateInput but haven't done so in our CiRunner type.

Currently we have:

CiRunner RunnerUpdateInput
projects ownerProject & associatedProjects

We aim to have

CiRunner RunnerUpdateInput
projects, ownerProject & associatedProjects ownerProject & associatedProjects

We described this here:

If down the line we see that an associatedProjects (i.e. projects minus ownerProject) is much more useful than a projects field, we can (...) add associatedProjects and deprecate projects (...).

Possible deprecations

  • projects may be deprecated here, as the separate owner and associated fields provides the same information.
Edited by 🤖 GitLab Bot 🤖