oxidecomputer / oxidecomputer/oxide-gha-runner-scale-set-controller
Support Oxide profile
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
There's no reason the controller can't retrieve its Oxide authentication from the credentials file instead of just values in the YAML or environment variables. Let's implement profile support.
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 controller's existing Oxide authentication handling for YAML and environment variables, then identify how credentials-file profile support should fit alongside them. Done means the controller can retrieve authentication from the credentials file as well as the existing sources, with coverage for the new behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100