Aias00 opened a new issue, #7296:
URL: https://github.com/apache/shenyu/issues/7296

   ## Background
   
   TARS plugin and starter snapshots already exist in 
`apache/shenyu-plugin-store` through PRs 
[#2](https://github.com/apache/shenyu-plugin-store/pull/2) and 
[#3](https://github.com/apache/shenyu-plugin-store/pull/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;
   - open bug #6738 must not be lost during the move.
   
   Depends on #7294.
   
   ## Scope
   
   ### plugin-store
   
   - Port all TARS changes made in `apache/shenyu` after plugin-store PR #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 regression coverage for #6738 and every post-copy TARS fix.
   - 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.
   - [ ] #6738 has a regression test and is resolved or explicitly carried as a 
blocker.
   - [ ] E2E proves registration/metadata, invocation, failure behavior, and 
hot config refresh.
   - [ ] A minimal ShenYu bootstrap works with the plugin-store TARS starter.
   - [ ] Maven publication ownership is switched atomically with no duplicate 
coordinates.
   - [ ] Main-repository removal occurs only after the external artifact and 
E2E are green.
   
   


-- 
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]

Reply via email to