You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TARS plugin and starter snapshots already exist in apache/shenyu-plugin-store through PRs #2 and #3. They are not yet the authoritative implementation:
the store copy predates recent fixes in apache/shenyu;
the store TARS POM explicitly skips Surefire tests;
there is no TARS E2E workflow in the store;
the implementation still depends on TARS-specific core enums, DTOs, constants, response handling, admin registration, and client modules;
Port all TARS changes made in apache/shenyu after plugin-store PR Dev jiangxiaofeng #2, including proxy initialization, empty proxy-list handling, selector/upstream updates, null handling, and resource cleanup fixes.
Remove the Surefire skip and make the existing plugin/starter tests pass in CI.
Add a TARS E2E environment covering provider startup, client/API registration or explicit metadata registration, selector/rule creation, successful invocation, no-result handling, failure handling, and dynamic metadata/config refresh.
Add documentation and an example bootstrap that consumes the external starter.
apache/shenyu and client/admin boundaries
Replace hard-coded PluginEnum.TARS, RpcTypeEnum.TARS, RPC response-writer entries, TARS DTOs/converters, and admin registration dependencies with the external-plugin contract.
Move or preserve TARS client registration in the authoritative client repository; do not leave duplicate published artifacts.
Remove TARS plugin/starter/default-bootstrap dependencies, examples, and duplicated integration tests from the main repository only after store parity passes.
Keep historical upgrade SQL; add a migration/compatibility note for existing TARS plugin data.
Acceptance Criteria
Store TARS source contains all fixes present on main at cutover time.
Unit and starter tests run rather than being skipped.
Background
TARS plugin and starter snapshots already exist in
apache/shenyu-plugin-storethrough PRs #2 and #3. They are not yet the authoritative implementation:apache/shenyu;Depends on #7294.
Scope
plugin-store
apache/shenyuafter plugin-store PR Dev jiangxiaofeng #2, including proxy initialization, empty proxy-list handling, selector/upstream updates, null handling, and resource cleanup fixes.apache/shenyu and client/admin boundaries
PluginEnum.TARS,RpcTypeEnum.TARS, RPC response-writer entries, TARS DTOs/converters, and admin registration dependencies with the external-plugin contract.Acceptance Criteria