Aias00 opened a new issue, #7301: URL: https://github.com/apache/shenyu/issues/7301
## Background `shenyu-plugin-logging-tencent-cls` is a Tencent Cloud-specific access-log sink. Its runtime is isolated behind `logging-common`, so ownership belongs in the plugin store rather than the gateway core repository. Related lifecycle issue: #6655. Depends on #7294. ## Scope ### plugin-store - Add the Tencent CLS logging plugin and Spring Boot starter. - Port all current fixes for configuration refresh, client initialization failures, time-unit conversion, asynchronous delivery, and shutdown. - Add unit tests for configuration validation, log-event mapping, topic/logset selection, batching, retry/error handling, dynamic config refresh, repeated start, and client cleanup. - Add a credential-free E2E/contract test with a local endpoint or SDK test double that proves gateway access logs reach the CLS client boundary. - Optionally add a secret-gated scheduled real-CLS smoke test. - Document credentials, region/endpoint, logset/topic configuration, payload fields, retry semantics, and supported versions. ### apache/shenyu - Remove plugin/starter/default-bootstrap dependencies after parity. - Update current enum/admin seed/menu/docs/dependency/license/distribution entries while retaining historical upgrade scripts. - Ensure the default bootstrap no longer contains the Tencent CLS SDK. - Add migration notes for existing selector and plugin configuration. ## Acceptance Criteria - [ ] Unit tests cover mapping, refresh, retry/failure, repeated start, and shutdown. - [ ] PR E2E requires no external account or long-lived secret. - [ ] Optional cloud smoke credentials are isolated and masked. - [ ] The external starter works with a minimal ShenYu bootstrap. - [ ] #6655 has regression coverage before cutover. - [ ] Publication ownership is switched without duplicate artifacts. -- 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]
