API to remove runners

[honx]

Feature Description

I'm running a gitea installation with a lot of "ephemeral" act_runners. These register, do work for a short amount of time and then get deleted. It seems there is currently no way to programmatically remove runners from repos/orgs and it has to be done by hand in the web ui.

The following functions would be really useful for me:
a) a way to retrieve runner info (esp. Status and "Last online Time") via the REST API
b) a way to delete runners via the REST API
c) a way for a runner to deregister itself via the grpc API (not a replacement for a) since the runner cannot be trusted to deregister itself)

I had look through the Rest API, grpc api and there currently (1.24 dev) doesnt seem to be a way to do this. I also didnt find any issues for gitea or act_runner that already discuss this.

Screenshots

No response

[ChristopherHX]

I came around an ephemeral runner management application that actually used the runners rest api of GitHub Actions just this week. Mounting this into Gitea Rest would be great, otherwise the runner list cleanup logic fails.

Those apis I would suggest are based on GitHubs like

• List https://docs.github.com/de/rest/actions/self-hosted-runners?apiVersion=2022-11-28#list-self-hosted-runners-for-an-organization
• Delete https://docs.github.com/de/rest/actions/self-hosted-runners?apiVersion=2022-11-28#delete-a-self-hosted-runner-from-an-organization

A marker for myself

gitea/routers/web/shared/actions/runners.go

Line 296 in ae4a3d7

func RunnerDeletePost(ctx *context.Context) {

I wanted to have c) as fallback of missing server support for ephemeral WIP, but now it's to late for my usecase as no ephemeral support most likely implies no self remove.

[ChristopherHX]

For what it worth here a draft of an organization + repository level implementation of 1) and 2) ChristopherHX@fe4f407 + ChristopherHX@624fde6 (to fix the labels getter)

This area is currently in flux, while my other changes are pending.

[honx]

@ChristopherHX Thanks for the feedback! So this means you're already working on that? I may actually also put some work into this. But I cannot really say if i find the time so this can still make it into 1.24...

[ChristopherHX]

So this means you're already working on that?

Yes for 1) and 2) I did start, but open points are

• swagger documentation
• reject deleting active runners (the webui does not check anything)
• Ephemeral json field depends on an active PR
  • Either hardcode it to false as long it is missing
  • or wait for it be reviewed before creating a PR
• write tests

I would leave point 3) open, because there are much more repositories involved in changing the grpc API. (I did go through this process recently for ephemeral, that is still pending)

If you want to give 3) a go feel free to look into it.