Aias00 opened a new issue, #7305: URL: https://github.com/apache/shenyu/issues/7305
## Background Polaris is not a single runtime plugin. ShenYu support spans admin listener, data-sync client, registry integration, Spring Boot starter, configuration, tests, and default-bootstrap dependencies. Its ecosystem is narrower than the default HTTP/WebSocket/ZooKeeper/Nacos paths, so it should be maintained as an optional extension stack. This task intentionally treats Polaris as one vertical integration and must not move only one Maven module. Depends on #7294. ## Scope ### plugin-store - Add an agreed top-level layout for non-request plugins/extensions. - Migrate the Polaris admin listener, gateway data-sync module, registry/instance integration, Spring Boot starter, configuration objects, and all owned tests. - Preserve current namespace, cache-removal, reconnect, watcher, and delete-event behavior. - Add unit tests for serialization/path handling, listener updates/deletes, namespace isolation, reconnect, watcher cleanup, and close/shutdown. - Add an integration/E2E environment with a disposable Polaris server, ShenYu admin, and gateway. Verify initial sync, plugin/selector/rule create-update-delete, namespace isolation, reconnect/recovery, and clean shutdown. - Document Polaris server/client versions, authentication, namespace mapping, deployment, and ShenYu compatibility. ### apache/shenyu - Remove all four Polaris integration surfaces and the default-bootstrap starter only after external parity: admin listener, sync-data-center, registry/instance support, and starter. - Update dependency management, configuration docs, examples, CI matrices, LICENSE/NOTICE, and distribution packaging. - Preserve historical upgrade/configuration documentation and add a cutover guide. - Confirm that removing Polaris does not affect default HTTP/WebSocket or other sync channels. ## Acceptance Criteria - [ ] The complete Polaris vertical stack is owned and built in one repository. - [ ] Unit tests cover create/update/delete, namespace isolation, reconnect, and cleanup. - [ ] E2E proves admin-to-gateway synchronization through a real disposable Polaris service. - [ ] Default sync channels pass regression tests after main-repository removal. - [ ] A minimal gateway can enable Polaris solely by adding the external starter. - [ ] Artifact publication and removal are rollback-safe and do not duplicate coordinates. -- 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]
