Repository navigation
[ISSUE #7599] Receive the complete Apollo registry and data-sync integration - #28
yangjj-iso wants to merge 3 commits into
Conversation
|
The receiving Build workflow is still awaiting maintainer approval. Could a maintainer please approve it so the Apollo extension can receive upstream CI validation? The contributor account receives 403 when requesting workflow approval. The paired main removal #7628 has been synchronized and validated locally, but remains draft. This request does not waive the preceding deprecation release, publication/coordinate ownership or rollback requirements. |
|
Updated validation request for current head f6bf126: the Build run https://github.com/apache/shenyu-plugin-store/actions/runs/41361429919 remains action_required. Could a maintainer approve it so the current external Apollo stack, including the .list key handling and snapshot-compatible deletion tests, receives hosted CI validation? The paired core PR apache/shenyu#7628 is now ready for code review, and its newly fixed Admin, HTTP-sync starter and Java 21 plugin tests have passed in the current CI run. Its IT workflow has also passed; remaining CI/E2E work is still running. Those core results do not replace this receiver's validation. The completed deprecation release, published compatible artifacts with unique ownership, deployment checks and rollback announcement remain required before the core removal can merge. |
Receive the complete Apollo integration for apache/shenyu#7599: registry, gateway data synchronization, Admin listener and Spring Boot starter. Paired core cutover: apache/shenyu#7628.
Preserve the apollo SPI/type, namespaces, key layout and Apollo SDK configuration. The external synchronization adapter now carries the upstream .list index-key correction: legitimate plugin/selector/auth names ending in list still receive add/update/delete events. Tests retain the key-derived deletion identity across the supported older/current core snapshot DTO shapes.
Fresh verification selected all four receiving modules explicitly, including registry and listener modules. Unit, local SDK/configuration integration, external SPI and starter tests passed on Java 17, with Checkstyle and RAT. The transfer does not depend on the remaining in-tree Apollo implementation.
Ready for formal code review. Merge/release still requires coordinated compatibility, publication with unique ownership, the completed deprecation cycle for the main removal, passing deployment CI and an announced rollback window. Local SNAPSHOT installation is not a published release. No artifact publication or fresh full Docker deployment result is claimed; the main cutover must not merge in its deprecation release.