qqeasonchen opened a new pull request, #5344: URL: https://github.com/apache/eventmesh/pull/5344
Part of #5296 (Architecture Review, Q2 2026-09-07). Closes #5338. Before this commit, `DeliveryTopology` was a documented enum but the `eventmesh.delivery.topology` config key was never actually read - the `EventMeshApplication` ctor called the 6-arg `UniRuntime` overload that hard-codes `LOCAL_STICKY_PULL`, regardless of operator configuration. This commit: 1. `eventmesh.properties` - new commented section `eventmesh.delivery.topology=LOCAL_STICKY_PULL` with inline explanation of both modes, the env-var / -D override, and the fail-fast behavior on unknown values. 2. `EventMeshApplication.java` - read `eventmesh.delivery.topology` from system properties via `DeliveryTopology.fromConfig(...)` and pass to the full 7-arg `UniRuntime` ctor. Missing / blank -> LOCAL_STICKY_PULL (backward compatible). Unknown -> fail-fast IllegalArgumentException. 3. `docs/control-plane.md` - new page documenting for `DeliveryTopology` and `SecurityGate`: configuration key, default value, failure behavior, and coverage per ingress route (HTTP / A2A / TCP / WebSocket / SSE / Admin / Connector Runtime). ## Acceptance check for #5338 - [x] `eventmesh.delivery.topology` is documented in `eventmesh.properties` with the LOCAL_STICKY_PULL default and a fail-fast note. - [x] `EventMeshApplication` reads the key and passes the resolved topology to `UniRuntime`'s full constructor. - [x] `docs/control-plane.md` lists every ingress route and the gate it goes through, with the default + failure behavior per component. ## Note PARTITION_OWNED_PULL wiring is tracked in #5309. Once #5309 lands, the control-plane doc's PARTITION_OWNED_PULL row moves from "code intact, wiring pending" to "fully wired". -- 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]
