oxidecomputer / oxidecomputer/oxide.rs
add `oxide env` subcommand to populate environment with OXIDE_HOST and OXIDE_TOKEN variables
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 75
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
I've found something like this (https://github.com/transposit/awscli-as-session) to be useful for running terraform e.g. oxide env terraform plan would run terraform with OXIDE_HOST and OXIDE_TOKEN set in that environment. This will further be useful when Oxide supports MFA, and keys that expire.
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
The issue names no files or tests; begin by locating the CLI entry point and existing authentication or environment handling. Define and verify oxide env terraform plan with OXIDE_HOST and OXIDE_TOKEN populated, including behavior when credentials are unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100