oxidecomputer / oxidecomputer/helios
Expose Illumos commit used in builds in helios.json
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 481
- Forks
- 21
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 2
Description
Currently the helios.json file generated during TUF repo builds does not list the illumos-gate commit it used.
This can be found by searching for os_short_commit in the build log as below, but it would be more convenient if we showed it more directly.
[8511](https://buildomat.eng.oxide.computer/wg/0/details/01JVJTA28DEMM4C4ARXQ5W5WWX/3iCCLG9ZSw1N5rB3A5vMPbhfyl2plK7Ey3nKO8G0dR53pl14/01JVJTABRHWDD246MWWB6HACXJ#S8511) 2025-05-18T23:52:40.087Z [ recovery-image] May 18 23:52:39.356 INFO expanded image name: "recovery dbb6669/${os_short_commit} 2025-05-18 23:17" -> "recovery dbb6669/361574b 2025-05-18 23:17"
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
Locate the code that generates helios.json during TUF repository builds, then search the repository for os_short_commit to trace where the Illumos commit is already available. Update the generated metadata to include that commit and verify the resulting helios.json or relevant build validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100