influxdata / influxdata/openapi
Update Routes.yml for backup, restore, labels, notificationRules, notificationEndpoints, scrapers, swagger, checks, plugins, delete, ready
@devanbenz is already working on this.
Since May 8, 2026.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
The routes in the OSS are missing a lot of entries. We need to add them, and regenerate `swagger.json`.
- The /ready path is documented upstream (in oss/ready.yml).
- The Routes schema that backs the GET /api/v2 links response does not include ready.
If you add "ready": "/ready" to apiLinks["system"] in http/api_handler.go, the actual response will contain a key that isn't declared in the schema — a small divergence that's already present for many other keys (backup, restore, labels, notificationRules, notificationEndpoints, scrapers, swagger, checks, plugins, delete).
Update Routes.yml . A small PR against influxdata/openapi adding ready to system.properties, then regenerate influxdb/static/data/swagger.json
Contributor guide
No contributing guide indexed for this repository
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.