Hello everyone!
I realize this is likely a bit different, but I’m working on a BOSH deployment for Gitea and the runners. What’s different here is that none of the servers are touched or hand-configured – they are all managed via manifests (yaml files).
I have Gitea up and running without issue. I’m a bit stuck with the act_runner, however. I’m setting this up to allow the runners to be on a separate VM (so they can scale to multiple VMs if required).
But… I’m uncertain how to approach the registration token. I can’t find a way to set it. Since there isn’t any manual configuration of the VMs, I can’t manually copy/paste the token from the UI.
I did find the /admin/runners/registration-token API call. But I need authentication for that, and it doesn’t appear to be the “SECRET_KEY” or “INTERNAL_TOKEN”. The only thing I have is that I can authenticate with a user. So maybe I have to create some dummy user with a known password (to the deployment, not by humans).
Is there a better way to get this configured? Seems like I’m missing a step. Is there a way to “pre-authorize” a runner from the Gitea command-line itself? I would know the host name or the IP address as part of the deployment automation.
Thanks!
-Rob