yuluo-yx opened a new issue, #2914: URL: https://github.com/apache/rocketmq-dashboard/issues/2914
The K8s certificate and cloud credential repositories first check whether a non-null id still exists, then insert when it does not. An update request racing with deletion can therefore insert a new row using the stale id and recreate a resource that was already deleted. Reproduction: 1. Load an existing certificate or cloud credential for editing. 2. Delete it in another request. 3. Submit the stale update carrying its original id. Actual: the repository follows the insert path and can recreate the deleted row. Expected: a non-null id is always update-only; a zero-row update returns a conflict and never inserts. -- 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]
