oxidecomputer / oxidecomputer/oxide-cloud-controller-manager
Warn or error when --cloud-config is passed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2h 5m
- Merged PRs (30d)
- 14
Description
Context
The cloud provider registration func (internal/provider/provider.go) discards the io.Reader for the config file — configuration is entirely env-var based (OXIDE_HOST/OXIDE_TOKEN/OXIDE_PROJECT). A user passing --cloud-config gets silence: their config file does nothing and there's no hint why.
Scope
- Log a warning (or return an error) when the config reader is non-empty.
- Document in the README that configuration is env-var based and
--cloud-configis unsupported.
Done when
Passing --cloud-config produces visible feedback instead of silence.
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 in internal/provider/provider.go, where the cloud provider registration function receives the config io.Reader, then inspect the README configuration guidance. Trace how --cloud-config reaches that function and make sure a non-empty reader produces visible feedback. Done means passing --cloud-config warns or errors, and the README states that configuration uses OXIDE_HOST, OXIDE_TOKEN, and OXIDE_PROJECT instead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100