Oxidaner opened a new issue, #1581:
URL: https://github.com/apache/dubbo-admin/issues/1581
Parent: #1491
Phase 6 — management UI and end-to-end verification. This is the phase after
which the MVP is accepted as a whole.
### Scope
- Basic management UI for MCP servers: server and tool configuration,
availability state, contract warnings, credential management.
- MCP conformance tests.
- Equivalent Nacos/ZooKeeper Resource fixtures.
- Dual-protocol Java provider end-to-end tests.
- Multi-replica database testing and hardening.
### Acceptance criteria
- Management UI covers server/tool configuration, displayed availability
state, contract warnings and credential lifecycle, and surfaces audit
information.
- MCP conformance tests pass.
- Equivalent Nacos and ZooKeeper Resources produce the same catalog, schema,
binding and availability results.
- End-to-end scenarios of the proposal's §14 are covered, including at
minimum:
- `tools/list` returns the Published schema;
- a valid call reaches a provider through normal Dubbo routing, once for
`dubbo` and once for `tri`;
- taking all providers down keeps the tool listed during the grace period,
hides it after the grace period, and a call then returns `not-executed`;
bringing them back restores the tool;
- a simulated discovery outage yields `UNKNOWN`, keeps the tool listed and
emits a warning rather than blocking on publish;
- a provider version that no longer exports the target interface still
does not hide the tool (documented MVP gap) and the call returns `not-executed`;
- unknown nested fields are rejected before dispatch;
- a 19-digit `long` survives as a string into the provider;
- an input DTO change hides only that tool and leaves the sibling tools
working until republish;
- a return-value DTO change affects neither `tools/list` nor `tools/call`
and only raises a management-page warning;
- selecting an unexported protocol is rejected at publish time with a
clear reason;
- a response timeout causes no second provider to receive the call, for
both `dubbo` and `tri`.
- Multi-replica: two Admin replicas share one database; revoking a
credential on replica A invalidates it on replica B immediately, and two
concurrent publishes with the same stale `resourceVersion` produce exactly one
success.
- Any item not completed must be recorded as an explicit risk rather than
assumed to be supported.
### PR
- PR-9 — management UI.
- PR-10 — E2E, conformance, multi-replica hardening.
Dependency: Phase 1–5 (PR-1 … PR-8).
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]
