kong-sales-api/dev/gitrepository.yaml at 18a3a6488a1a15fc3c7204555764dc97ecd6781a - kong-sales-api - Gitea

stt/kong-sales-api

Files

T

Stéphane Tailland de69f88e29 Build sales-api REST + MCP layers (Layer 3), full build in one pass

14 routes: Order (single key, full CRUD + order-details sub-resource)
and Orderdetail (composite key ordernumber+productcode, own
top-level resource, mirrors backend's own URL structure). MCP layer
built with the corrected single-route pattern from the start
(STATUS.md section 18) — 7 tools, list/get read-only for all 5
roles, create-order/create-orderdetail for admin+customer+support
(verified against OrderPermission/OrderScopedPermission.check() —
support gets an unconditional class-level pass, the status-only
restriction is object-level and doesn't apply to create).

Keycloak (local): sales-api-audience + mcp-sales-audience client
scopes, sales-api + mcp-sales resource clients, attached to the
broker and librechat respectively. Deploy key and broker secret
reused/mirrored from catalog-api and the live broker client, same
pattern as customers-api/payments-api.

2026-08-23 17:02:17 +02:00

13 lines

259 B

YAML

Raw Blame History

 apiVersion: source.toolkit.fluxcd.io/v1
 kind: GitRepository
 metadata:
   name: sales-api-dev
   namespace: sales
 spec:
   interval: 5m
   url: ssh://git@gitea.sttlab.eu:2222/stt/kong-sales-api.git
   secretRef:
     name: sales-api-git-auth
   ref:
     branch: main