Docs: Add API document for runner controllers and tokens
What does this MR do and why?
This merge request adds API documentation for managing GitLab Runner Controllers and their authentication tokens.
The first document describes how to manage Runner Controllers, which are components that controls GitLab Runner jobs. It provides API endpoints to create, view, update, and delete these controllers, along with the ability to enable or disable them. Each controller has basic properties like a description, enabled status, and timestamps.
The second document covers the management of authentication tokens that Runner Controllers use. It includes endpoints to list existing tokens, create new ones, retrieve specific token details, revoke tokens when they're no longer needed, and rotate tokens for security purposes. When creating or rotating tokens, the actual token value is returned for use in authentication.
Both APIs require administrator access and are available only in GitLab's Ultimate tier for self-managed and dedicated instances. The documentation includes detailed examples showing the exact API calls, request formats, and expected responses, making it easy for administrators to integrate these features into their GitLab Runner management workflows.
References
Related MRs:
- Add runner controller management API (!210821 - merged)
- Add runner controller token API (!212730 - merged)
- Add revoke endpoint for runner controller token... (!215879 - merged)
- Add rotate endpoint for runner controller token (!217341 - merged)
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.