Aias00 opened a new issue, #852: URL: https://github.com/apache/rocketmq-dashboard/issues/852
### What happened RocketMQ Studio K8s certificate write APIs accept JSON literal `null` request bodies: - `POST /api/k8s-certs/create` - `POST /api/k8s-certs/update` - `POST /api/k8s-certs/renew` - `POST /api/k8s-certs/delete` The controller passes the DTO directly to `K8sCertService`, and the service logs fields such as `command.getName()` / `command.getId()` before any null guard. A null body can therefore fail as an internal `NullPointerException` instead of a structured 400 response. ### Expected behavior K8s certificate write APIs should reject missing or JSON `null` request bodies with a clear 400 response, and the service should also guard direct calls to avoid accidental NPEs. ### Why this matters Kubernetes deployment and certificate management are part of the Studio cloud-native control-plane surface. Invalid write requests should fail predictably and not surface implementation errors. ### Scope RocketMQ Studio / track 1 control-plane K8s certificate management. -- 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]
