Aias00 opened a new issue, #1998: URL: https://github.com/apache/rocketmq-dashboard/issues/1998
## Problem The local K8s certificate management contract has two data-integrity gaps: 1. Certificate creation requires non-blank `name`, `namespace`, `cluster`, and `issuer`, but partial updates accept blank strings for those same fields. A successful update can therefore persist an unusable certificate record with missing identity metadata. 2. Certificate deletion checks existence before deleting, but the repository discards the affected-row count. If two delete requests pass the initial lookup, the second request can delete zero rows and still return success and record a successful audit event. ## Expected behavior - Optional update fields keep `null` as “unchanged”, but supplied identity fields must contain non-whitespace text and should be normalized before persistence. - Repository deletion returns whether a row was actually removed. - A zero-row delete is reported as a structured 404 and does not emit a successful delete audit event. ## Scope Track 1 / K8s certificate inventory persistence. This does not implement Kubernetes or cert-manager mutations and does not overlap the provider-integration design in #1314. -- 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]
