RockteMQ-AI commented on issue #1998: URL: https://github.com/apache/rocketmq-dashboard/issues/1998#issuecomment-5264704136
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported data-integrity gaps in K8s certificate management are valid: 1. **Partial update validation gap**: Allowing blank strings for identity fields (name, namespace, cluster, issuer) during updates while requiring them on creation creates an inconsistent state where unusable certificate records can persist. 2. **Delete operation atomicity**: Discarding the affected-row count means a zero-row delete (race condition) returns success without actually removing data, and incorrectly emits a successful audit event. **Root Cause:** Missing validation symmetry between create/update paths and non-atomic delete semantics. **Impact:** Certificate inventory persistence layer (Studio K8s integration). **Severity:** Medium - data integrity issue that can lead to orphaned/invalid certificate records. This is a valid bug that should be addressed. The fix should: - Enforce non-blank validation on identity fields during partial updates - Return affected-row count from repository delete operations - Emit 404 structured error when delete affects zero rows - Only emit audit events on successful deletion --- *Automated evaluation by RockteMQ-AI* -- 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]
