Skip to content

Prepare register command to fail if runner server-side configuration options are passed together with a new glrt- token

Pedro Pombeiro (OOO from July 16th till Aug 7th) requested to merge pedropombeiro/29510/forbid-server-config into main

What does this MR do?

This MR prepares the register command to fail if the user tries to use a new glrt- runner token as a registration token, and at the same time tries to leverage the command line arguments to configure the runner on the server side (e.g. setting tags, paused, protected status, etc.)

Why was this MR needed?

See second paragraph in https://docs.gitlab.com/ee/architecture/blueprints/runner_tokens/#using-the-authentication-token-in-place-of-the-registration-token

What's the best way to test this MR?

  1. Try to pass any of the forbidden arguments when passing a fake registration that begins with glrt-;
  2. Try to pass the same arguments when using a normal valid registration token. This time registration should succeed.

What are the relevant issue numbers?

Closes #29510 (closed)

Merge request reports