Aias00 opened a new issue, #976:
URL: https://github.com/apache/rocketmq-dashboard/issues/976

   ## Problem\nSeveral write endpoints bind raw mutable VOs instead of 
validated request DTOs. Missing names, null payloads, and invalid rule fields 
reach services, repositories, or RocketMQ admin calls rather than failing as a 
clear HTTP 400.\n\n## Evidence\n-  accepts a raw  without .\n-  accepts raw  
and  for writes.\n-  accepts raw ; the VO has no constraints for name, 
operator, duration, or severity.\n\n## Impact\nInvalid requests can produce 
NPEs, persistence failures, downstream admin errors, or invalid exported 
Prometheus rules.\n\n## Expected behavior\nWrite APIs reject malformed bodies 
consistently before mutating state.\n\n## Proposed fix\nIntroduce 
operation-specific DTOs with Bean Validation, retain service-level guards, and 
add controller regression coverage for null, blank, and invalid 
enum/operator/duration inputs.\n\n## Scope\nStudio Track 1 resource and 
observability API reliability.


-- 
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]

Reply via email to