Disallow project runners from being unassigned from owner
What does this MR do and why?
We currently only allow disabling a runner from an associated project if there are other projects associated with the runner. I believe we should be a bit stricter, in order to preserve the ownership of the project runner, and only allow disabling a runner on non-owner projects.
Changelog: changed
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
- Disallow dissociation of project runners from o... (#517273 - closed)
- https://docs.gitlab.com/ee/api/runners.html#disable-a-runner-from-project
- https://docs.gitlab.com/ee/ci/runners/runners_scope.html#project-runner-ownership
- #517273 (comment 2337286582)
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
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
n/a
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
The behavior is already well covered with tests, which have been extended for this MR, so I don't think we need manual QA. Let me know if you think otherwise and I can provide the steps.