Files
zeekayandHanzo Dev 404de134f3 Point the API spec and its route checker at the new base
The OpenAPI document keys every operation by its full path, so the spec
described endpoints that no longer exist the moment the server moved.

The openApiSync analyzer cross-checks each registered subrouter against
that document and reconstructs the prefix from a literal of its own, so
spec and analyzer have to move together or every route reports as
missing. Its special case for the v5 root goes away with the root
itself.

The api/v4 directory keeps its name: it is where the spec sources live,
not a URL anyone requests.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-14 10:58:08 -07:00

26 lines
732 B
YAML

/v1/team/cluster/status:
get:
tags:
- cluster
summary: Get cluster status
description: >
Get a list of all healthy nodes, including local information and
status of each one. If a node is not present, it means it is not
healthy.
##### Permissions
Must have `manage_system` permission.
operationId: GetClusterStatus
responses:
"200":
description: Cluster status retrieval successful
content:
application/json:
schema:
type: array
items:
$ref: "#/components/schemas/ClusterInfo"
"403":
$ref: "#/components/responses/Forbidden"