Skip to content

Specify /runners/verify endpoint behavior in blueprint

Pedro Pombeiro requested to merge pedropombeiro/add-verify-behavior-to-blueprint into master

What does this MR do and why?

Describe in detail what your merge request does and why.

During discussions with frontend and UX counterparts, it came up that it would be a good idea to let the admin know that the runner was correctly registered while still on the runner creation page (where the runner registration command is displayed). In order to trigger an animation showing the completion of the process, we'd poll for a new ci_runner_machines record with the given runner token. In order to support this, we need to create the record in response to gitlab-runner register (i.e. POST /runners/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.

Merge request reports