oxidecomputer / oxidecomputer/oxide-gha-runner-scale-set-controller
Inject SSH keys for debugging
Open
Nobody has claimed this yet.
Enhancement
GitHub Actions Runner Scale Set Controller
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Let's support injecting SSH keys into the runner so people can connect to it to debug. We'll need to understand whether the runner stays alive long enough after a job to be debugged.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the runner lifecycle and determining whether the runner remains alive after a job completes. Then identify where SSH key injection and post-job debugging would fit, and define completion as a supported way to connect to the runner for debugging when the lifecycle permits it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100