oxidecomputer / oxidecomputer/omicron
in reconfigurator-cli tests, always run blippy when generating a new blueprint?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Follow up from https://github.com/oxidecomputer/omicron/pull/10408#discussion_r3210299212 -- the invalid blueprint is immediately caught by blippy. We should consider running blippy each time we do a planning run and (at least) print FATAL notes.
Contributor guide
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 with the reconfigurator-cli tests and the planning-run path referenced in the issue, then inspect how a new blueprint is generated and where blippy is currently invoked. Run the existing tests; done means blippy runs for every planning run and at least its FATAL notes are printed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100