-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated provisioning of Actions runners #24750
Comments
Isn't that already implemented by #23762? |
#23762 goes some way to making automation easier, but would still require executing the CLI in an automated fashion, extracting the token from the output, and applying it to the runner config, repeated for each runner. This would be particularly messy in an integration test. Since runner tokens are just fixed-length random strings, would it be acceptable to have admin-supplied tokens/scopes retrieved from the ini with the ability to be reused? |
perhaps me completing this PR #23761 would be helpful |
#23761 still suffers similar shortcomings in this context. We would need to provision an admin user, create an API token, and hit the API with that token for each runner. Perhaps fixtures are the answer, but that still leaves the issue of the tokens being one-time use, and would not alleviate the complexity of dynamically scaling runners outside of a test environment. |
Duplicate of #23703 |
So it is, bugger it. Thanks @benyanke 💙 |
Feature Description
Currently Actions runner tokens are retrieved from the web UI and are one-time use. This makes it difficult to provision runners in an automated fashion for CI and such.
Woodpecker and Drone accept a symmetic secret via environment variables for both the application and the runners, making automated provisioning zero-touch. Could such a flow be considered for Gitea please?
P.S. Since it's Gitea issuing and validating the tokens it seemed more appropriate to open this issue here, but I'm happy to move or open a companion issue on act_runner instead 👍
Screenshots
No response
The text was updated successfully, but these errors were encountered: