Problem to solve

As a developer interacting with a public repository, I want to be able to have ephemeral instances so that I can safely use self-hosted runners in a public repo.

Intended users

Any public repository user where github actions are used, and the default github hosted runners do not provide sufficient resources.

Proposal

• Have a warm pool of idling runners waiting for a job from github (polling sqs queue or something)
• When a idling runner gets a job, execute that job, and delete the runner when finished (the lifetime of the runner is the same as the GHA job it is executing)

What does success look like, and how can we measure that?

• Jobs are quickly executed since runners are pre-provisioned
• Security concerns over persistence of data across jobs are addressed since the lifetime of runners are tied to a single github job.