oxidecomputer / oxidecomputer/dice-util
permslip signer clutters stdout
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 3
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 16
Description
This is cosmetic. The permslip signer dumps some stuff to stdout that we should ignore. Instead it ends up cluttering output from the manufacture command:
$ dice-mfg manufacture --require-release-policy false permslip
sending ping ... success
setting platform id to: "PDV2:PPP-PPPPPPP:RRR:0000000000B" ... success
getting CSR ... success
checking CSR ... success
Wrote to 0000000000B/ca.cert.pem
setting Intermediate cert ... success
Wrote to 0000000000B/PDV2:PPP-PPPPPPP:RRR:0000000000B.cert.pem
success
setting PlatformId cert ... success
sending Break ... success
The lines we should be ignoring are: Wrote to 0000000000B/ca.cert.pem and Wrote to 0000000000B/PDV2:PPP-PPPPPPP:RRR:0000000000B.cert.pem. Looks like there's an extra success message too?
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 running the shown dice-mfg manufacture --require-release-policy false permslip command and tracing where the permslip signer writes its output. The work is done when the two Wrote to lines and any unintended extra success no longer clutter manufacture's stdout, while the intended status messages remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100