Oxidaner opened a new issue, #1577:
URL: https://github.com/apache/dubbo-admin/issues/1577

   Parent: #1491
   
   Phase 3 — control-plane APIs. This phase only creates and manages 
configuration; it does not make a business MCP endpoint callable.
   
   ### Scope
   
   - Server control plane: create/read/update Draft, **Validate**, **Publish**.
   - Nested Tool management endpoints under the server aggregate:
     - `GET/POST /api/v1/mcp/servers/{serverId}/tools`
     - `GET/PUT/DELETE /api/v1/mcp/servers/{serverId}/tools/{toolId}`
     - `POST /api/v1/mcp/servers/{serverId}/tools/{toolId}/validate`
   - Credential API, including revoke.
   - Control-plane audit events.
   - Console service/handler/router wiring.
   
   ### Acceptance criteria
   
   - Tool CRUD always goes through the server's `expectedResourceVersion` CAS. 
Tool endpoints do not bypass the server aggregate and do not create an 
independent transaction.
   - Publish re-validates the complete configuration and atomically replaces 
the Published snapshot through the `ResourceStore` CAS.
   - A publish that fails validation leaves the previous Published snapshot 
completely untouched.
   - A stale `expectedResourceVersion` returns **409**.
   - Deleting a server performs an atomic cascade over its tools and 
credentials.
   - Control-plane audit events are emitted and carry the acting principal.
   - Existing `/api/mcp` routes, Console authentication and the Generic Invoke 
API behave exactly as before (no behavioral regression).
   
   ### PR
   
   PR-4 — Console service/handler/router, Tool endpoints, atomic cascade on 
server delete, 409 conflict handling, audit fields.
   
   Dependency: Phase 1–2 (PR-1, PR-2, PR-3).
   
   Detailed design: [proposal §15 (line 
1243)](https://github.com/Oxidaner/dubbo-admin/blob/213bd38dbcfbe0c5bac64c7c8b949651f1633ca9/docs/proposal/mcp-server-proposal.md?plain=1#L1243)
 — design PR #1541.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to