From 28da1d0e10e2cdcea6845c8ff605c094c72e8705 Mon Sep 17 00:00:00 2001 From: Stepan Rabotkin Date: Tue, 1 Sep 2026 16:15:16 +0300 Subject: [PATCH] fix(openapi): give /osd/modify and /data/fix unique operationIds Duplicate operationIds are forbidden outright by the OpenAPI specification: the field must be unique among all operations in the document. Two endpoints violated it by carrying the id of their neighbouring delete operation, most likely copy-paste leftovers: /osd/modify was osdDelete and /data/fix was dataDelete. Rename them to osdModify and dataFix. Client generators derive method names from operationId, so besides restoring validity this stops the duplicates from silently colliding or being renamed by the generator. Signed-off-by: Stepan Rabotkin --- src/cmd/openapi.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/cmd/openapi.json b/src/cmd/openapi.json index 81538640..e05c2cdc 100644 --- a/src/cmd/openapi.json +++ b/src/cmd/openapi.json @@ -325,7 +325,7 @@ } }, "/osd/modify": { "post": { "summary": "Modify OSD reweight, tags or noout flag", - "operationId": "osdDelete", + "operationId": "osdModify", "consumes": [ "application/json" ], "produces": [ "application/json" ], "requestBody": { "content": { "application/json": { "schema": { @@ -597,7 +597,7 @@ } }, "/data/fix": { "post": { "summary": "Fix inconsistent objects in the cluster by deleting some copies", - "operationId": "dataDelete", + "operationId": "dataFix", "consumes": [ "application/json" ], "produces": [ "application/json" ], "requestBody": { "content": { "application/json": { "schema": { -- 2.47.3