Files
kong-catalog-api/openapi.yaml
T
Stéphane Tailland c210ffbaae Regenerate the spec against the gateway, not the backend
This spec predated the other four and documented the wrong surface: the
paths were the backend's (/classic-models/api/v1/...) and the server was
http://localhost:8000. Neither is reachable from the developer portal,
so every operation it published failed as written — the gateway serves
/catalog/v1/... and rewrites onto the backend path upstream.

Regenerated the same way as the other four domains: from the backend's
drf-spectacular schema, filtered to the operations this domain's gateway
exposes, derived from the Kong routes and their request-transformer
rewrites in Konnect. All 14 REST routes resolved to a backend operation.
Same six paths as before, now expressed as the gateway's, with
https://catalog-dev.sttlab.local as the server and path parameters
renamed to the gateway's capture names.

The five published specs now follow one convention.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-27 06:42:02 +02:00

19 KiB