oxidecomputer / oxidecomputer/omicron
Some Omicron zone files go into weird locations in the file hierarchy
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Originally posted by @jclulow in https://github.com/oxidecomputer/omicron/pull/7244#discussion_r1884622140
We often copy files like SMF manifests or schema files into the Omicron zone tarballs. Some of those seem to go into surprising locations, as Josh noted in the comment above. We might want to audit and move those to more suitable places.
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 locating how Omicron zone tarballs assemble copied SMF manifests and schema files, then inspect the resulting file hierarchy for surprising destinations. Done means the affected files are audited and moved to suitable locations, with the relevant build or packaging checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100