oxidecomputer / oxidecomputer/omicron
Do not use names in sagas
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Operate on UUIDs, not names, in sagas - this avoids a scenario where a saga is created to operate on an object named Foo, but the original object named Foo is deleted and another object is created that is also named Foo. The saga will end up operating on the wrong object.
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
No file, test, or entry point is named in the issue. Trace where sagas capture object names and where they resolve targets; the work is done when the original object's UUID remains the identifier and deleting and recreating an object with the same name cannot retarget the saga.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100