oxidecomputer / oxidecomputer/omicron
Blueprints: Record collection ID used in generation
@jgallagher is already working on this.
Since Feb 6, 2024.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In the update huddle today, we discussed keeping either (a) the collection used to generate the current target blueprint or (b) a higher number of historical collections. We're on the fence about (a); (b) seems fine but it's not entirely clear how high we'd have to bump it to be useful in practice.
At a bare minimum, we can easily add the collection ID that was used when a blueprint was generated to the serialized blueprint. This may not be very useful if the collection it references has already been pruned, but it's cheap and doing so might end up giving us more insight into (a) or (b) above.
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.
Assessment
This issue has not been assessed yet.