oxidecomputer / oxidecomputer/omicron
Should `omicron-package install` check for stale artifacts?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Part of the dev cycle for omicron is to use omicron-package to uninstall and reinstall the control plane. If one makes changes locally but forgets to rerun omicron-package ... package before the next install, the installation will proceed with the most-recently-built artifacts. Would it make sense for omicron-package ... install to check if it looks like omicron-package ... package needs to be run (and probably fail, with a flag to ignore this check)?
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 by tracing the omicron-package ... install and omicron-package ... package entry points and how they identify artifacts. Determine what stale state can be detected and how an override flag should behave; done means install warns or fails for stale artifacts while allowing the documented override.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100