oxidecomputer / oxidecomputer/omicron
Audit log: log ID of created resource
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
For actions that create a resource, like disk or instance create, we need to at least log the ID of the resource created. Even for token and session creation, we can probably log the ID of the created token or session. We may also want to log names if we have them for usability, especially in the case where the resource in question has been deleted, which means it can't be retrieved by the ID we logged.
Followup to https://github.com/oxidecomputer/omicron/pull/7339.
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 tracing how audit events are recorded for resource-creation actions, including disks, instances, tokens, and sessions. Identify the existing audit-log entry points and tests, then verify that created resource IDs are recorded consistently and assess whether names should also be included, including cases where resources are later deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100