-
Notifications
You must be signed in to change notification settings - Fork 990
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
Update runner to handle Dotcom/runner-admin based registration flow #2487
Conversation
Delete | ||
} | ||
|
||
public class RunnerDotcomServer : RunnerService, IRunnerDotcomServer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! I like the refactor to it's own class
|
||
public List<TaskAgent> ToTaskAgents() | ||
{ | ||
List<TaskAgent> taskAgents = new List<TaskAgent>(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Resolves: https://github.com/github/actions-runner-admin/issues/120
Add to runner settings property to identify if we register this runner via runner-admin and not Actions Service. Value of this property comes from dotcom side, where it is defined as feature flag. This value can't be provided via configuration argument. In future this will define behaviour of whole runner flow (assignment, deletion, etc.)
Add class to make call to dotcom. Add there functions to get runnergroups, list runners and add new runner. Right now we don't implement update of runner (replacement of runner if runner with provided name already exists during runner registration).