Draft: Move towards the concept of a runner deployment token
What does this MR do and why?
Describe in detail what your merge request does and why.
This MR updates the Runner registration token blueprint to include @josephburnett's suggestion to do away with the authentication token rather than the registration token.
Latest documentation preview link: http://main-ee-104273.docs.gitlab-review.app/ee/architecture/blueprints/runner_tokens/index.html
If this is merged, we'll also need to revise the following deliverables:
-
Deprecation files introduced in %15.6:
-
Deprecate
POST /api/v4/verify
endpoint
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Part of https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28915, https://gitlab.com/gitlab-org/architecture/tasks/-/issues/27