oxidecomputer / oxidecomputer/sush
Integrate with Oxide CLI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
To avoid customers needing to go fetch a separate binary, we should integrate the client library into the Oxide CLI.
Since customers won't be doing signing, it may be better to decouple the client library from permlip's, and instead shell out to a permslip binary.
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 reading the Oxide CLI repository and the client library integration described in this issue, focusing on the boundary between the CLI and the permslip binary. Clarify whether the CLI should embed the library or shell out to permslip; done means customers no longer need to fetch a separate binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100