youngkermit8-coder opened a new pull request, #4555: URL: https://github.com/apache/rocketmq-dashboard/pull/4555
K8s certificate private keys are already write-only in JSON responses, but Lombok still included `keyPem` in the generated string output of the create request, response/service value object, and persistence entity. Those representations can reach logs or diagnostic contexts. ## What changed - Exclude `keyPem` from `CreateCertDTO.toString()`. - Exclude `keyPem` from `K8sCertVO.toString()` while preserving the existing write-only JSON contract. - Exclude `keyPem` from `RmqK8sCertificate.toString()`. - Add a regression test that verifies each representation retains `k8sId` but never contains the private-key value. ## Scope This is a string-representation hardening change only. It does not change persistence, JSON payloads, certificate parsing, or Kubernetes integration. ## Verification - Focused regression test: 3/3 passed after demonstrating 3/3 baseline failures. - K8s controller/service/repository regression set: 42/42 passed. - Full backend suite on latest `rocketmq-studio`: 2417/2417 passed, 0 failures, 0 errors. - Production package: passed. - Checkstyle: 0 violations. - DCO sign-off included in the commit. -- 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]
