Aias00 opened a new issue, #2747: URL: https://github.com/apache/rocketmq-dashboard/issues/2747
## Problem Cloud credential deletion checks whether an instance currently references the credential and then deletes it in a separate operation. Cloud instance creation reads the credential, performs remote catalog work, and saves the instance later. Without a database foreign key or shared transactional lock, these operations can race and leave an instance referencing a deleted credential. ## Evidence - `server/src/main/java/org/apache/rocketmq/studio/provider/credential/CloudCredentialService.java:123` - `server/src/main/java/org/apache/rocketmq/studio/instance/InstanceService.java:178` - `server/src/main/java/org/apache/rocketmq/studio/instance/InstanceService.java:322` - `server/src/main/resources/db/schema.sql:71` ## Expected behavior - Database-level referential integrity prevents deleting a credential referenced by an instance. - Concurrent create/delete resolves to either a valid instance+credential pair or a clear conflict; never a dangling reference. - Existing databases receive an idempotent migration after orphan validation. - Add concurrency/integration coverage for both operation orderings. -- 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]
