oxidecomputer / oxidecomputer/falcon
Image management could be less opaque
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 5
- Avg merge
- 11d 13h
- Merged PRs (30d)
- 2
Description
During the process of building out new falcon images (debian-12, new arista image based on deb12), it has been difficult to understand where images are stored locally, what the contents of the image are (e.g. hash), when it was last updated (e.g. mtime) and how to update/replace an instance of an image that is already cached.
It would be really nice for the ability to query image details somewhat baked into a falcon binary (perhaps via the info subcommand or via a new images subcommand), and possibly even have an interface to manually trigger removal/refresh of the images.
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 at the falcon binary's command entry points and inspect how image storage and caching are currently handled. Compare an info subcommand with a new images subcommand, covering local location, contents or hash, modification time, and removal or refresh. Done means the issue's requested image details and cache controls have a defined, usable interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100