yyqdbngt opened a new issue, #2213: URL: https://github.com/apache/rocketmq-dashboard/issues/2213
## Problem `InstanceProviderRegistry` registers providers and cloud catalogs by repeatedly calling `EnumMap.put`. If two Spring beans claim the same `InstanceVendor`, the later bean silently replaces the earlier one. The selected implementation then depends on dependency-injection ordering, which makes a configuration error difficult to diagnose and can route requests to an unintended provider. ## Proposed scope - Fail fast while constructing the registry when duplicate instance providers claim a vendor. - Apply the same validation to duplicate cloud catalog providers. - Include the vendor in a stable, actionable exception message. - Add focused tests for normal registration and both duplicate cases. ## Expected behavior At most one provider and one catalog may be registered for each vendor, and ambiguous registrations should stop application startup deterministically. -- 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]
