You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/12 09:06:11 UTC

[I] [Studio][Bug] Preserve K8s certificate mutation integrity [rocketmq-dashboard]

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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Studio][Bug] Preserve K8s certificate mutation integrity [rocketmq-dashboard]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #1998:
URL: https://github.com/apache/rocketmq-dashboard/issues/1998#issuecomment-5349552010

   This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Studio][Bug] Preserve K8s certificate mutation integrity [rocketmq-dashboard]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #1998: [Studio][Bug] Preserve K8s certificate mutation integrity
URL: https://github.com/apache/rocketmq-dashboard/issues/1998


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Studio][Bug] Preserve K8s certificate mutation integrity [rocketmq-dashboard]

Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org