Aias00 opened a new issue, #7302: URL: https://github.com/apache/shenyu/issues/7302
## Background `shenyu-plugin-logging-huawei-lts` is a Huawei Cloud-specific logging sink and is not part of the ShenYu core request path. It has recent configuration and long-log handling fixes that must be preserved during migration. Related lifecycle issue: #6655. Depends on #7294. ## Scope ### plugin-store - Add the Huawei LTS logging plugin and Spring Boot starter. - Port all current main-branch behavior, including generic Huawei configuration fields, extra-long-log handling, client-init failure handling, time-unit correctness, and shutdown. - Add unit tests for configuration validation, log-group/stream mapping, long-log policy, batching, retry/failure, dynamic refresh, repeated start, and cleanup. - Add a credential-free PR E2E/contract test using a local controllable endpoint or SDK abstraction. - Optionally add a secret-gated scheduled LTS smoke test. - Document authentication, region/endpoint, log group/stream, long-log behavior, payload schema, and supported SDK/ShenYu versions. ### apache/shenyu - Remove plugin/starter/default-bootstrap dependencies after store parity. - Update current enum/admin seed/menu/docs/dependency/license/distribution entries, retaining historical upgrade SQL. - Ensure the default distribution no longer contains Huawei LTS SDK artifacts. - Document migration of existing plugin configuration. ## Acceptance Criteria - [ ] Recent Huawei-specific fixes are present and regression-tested in the store. - [ ] Unit tests cover long logs, refresh, failure, repeated start, and shutdown. - [ ] PR E2E uses no real cloud credentials. - [ ] Optional real-cloud checks keep credentials in protected GitHub environments. - [ ] A minimal gateway emits logs through the external starter. - [ ] #6655 has lifecycle regression coverage before cutover. - [ ] Artifact publication and main removal are coordinated. -- 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]
