Tools exist for inspecting self-hosted runner pools, sessions, secrets and logs.
Runner admin tools are defined, including moving a session between runners; reachability is undetermined.
What's wrong with this entry?
A group of tools for inspecting self-hosted runner setups now exists: read pool state, list runners, sessions and secrets, tail logs, start a local runner, and one write action that moves a session onto a different runner. Their descriptions state that secret values are never returned and that they authenticate with the operator's existing login. Whether these are reachable by ordinary users is not settled by the tool definitions themselves.
self_hosted_runner_requeue_session
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner