Aias00 opened a new issue, #7303: URL: https://github.com/apache/shenyu/issues/7303
## Background Apache Pulsar is active infrastructure, but `shenyu-plugin-logging-pulsar` is an optional sink adapter rather than gateway-core behavior. The migration is about repository ownership and dependency isolation, not ecosystem deprecation. Related lifecycle issue: #6655. Depends on #7294. ## Scope ### plugin-store - Add the Pulsar logging plugin and Spring Boot starter while consuming the supported `logging-common` API. - Port current fixes, including duplicate shutdown-hook removal and client-init failure handling. - Port and expand unit tests for producer configuration, topic selection, event serialization, batching, send failure, broker unavailability/recovery, dynamic config refresh, repeated start, and shutdown. - Add Testcontainers-based E2E with a real Pulsar broker. Start a gateway with the external starter, generate traffic, consume and assert the access-log event, update plugin configuration, and verify clean shutdown. - Document broker/auth/TLS configuration, payload schema, delivery guarantees, backpressure/retry behavior, and version compatibility. ### apache/shenyu - Remove the Pulsar logging plugin/starter/default-bootstrap dependency after parity. - Update current enum/admin seed/menu/docs/dependency/license/distribution entries while keeping historical SQL. - Ensure the default distribution no longer pulls Pulsar client artifacts. - Document existing selector/config migration and artifact coordinates. ## Acceptance Criteria - [ ] Unit tests cover serialization, refresh, broker failure/recovery, repeated start, and cleanup. - [ ] E2E uses a real disposable Pulsar broker and verifies the emitted record. - [ ] Shutdown leaves no duplicate hook, producer, or executor. - [ ] #6655 is fixed or protected by regression coverage. - [ ] The external starter works with a minimal bootstrap. - [ ] Store publication precedes coordinated main-repository removal. -- 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]
