oxidecomputer / oxidecomputer/omicron

Alerts and webhooks endpoints missing `/system` prefix

Open
#11,206 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

They have a system/alerts tag and as far as I know the resources are fleet-scoped, so we will probably want to add the prefix. API versioning should make it not too a big deal for clients.

https://github.com/oxidecomputer/omicron/blob/229ae4c00848d6c27760b159731d33cbfbf1693c/nexus/external-api/output/nexus_tags.txt#L183-L200

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked section of nexus/external-api/output/nexus_tags.txt and trace how the system/alerts tag maps to the alerts and webhooks endpoint paths. Confirm the intended fleet-scoped paths and API-versioning behavior; done means both endpoints include the /system prefix without breaking the generated external API.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, backend-api-design
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.