@mbestavros That shouldn't be a problem. Just get it into the kickstart and we should be good to go!
In other words, if the container stops, we can invoke the same command (with the same token) after a reboot to restart the same runner, with the same name. We shouldn't need any manual interaction apart from initially provisioning the token.
I'm looking at the kickstart now!
@npmccallum I'm forgetting... is there a way to provide input/arguments to the kickstart? Not just for the token, but also for runner names...
Yes and no.
Don't worry about it.
Just presume the token is in a file on the disk somehow.
An unexpected error occurred when executing this workflow. Please submit a new support request using our Support website:
Please include this unique ID in your request: 3E09:14F5:1AE197:1CCCFE:5EBEFC75
@npmccallum oh my... looks like I have to expand the macros with cargo expand...
@npmccallum we can't test, that something doesn't compile, or can we?