RockteMQ-AI commented on issue #3169:
URL: 
https://github.com/apache/rocketmq-dashboard/issues/3169#issuecomment-5545835611

   **Issue Evaluation**
   
   Category: `enhancement` | Status: **Evaluated**
   
   **Feasibility:** feasible
   **Scope:** Cloud credential settings tab (frontend + backend API for 
credential-instance correlation)
   **Compatibility:** no breaking changes — read-only addition, does not modify 
credential CRUD or instance bindings
   
   This is a well-scoped operator visibility feature. The proposed design 
covers the key aspects:
   
   - **Used / unused / vendor-mismatched classification** — straightforward to 
implement by cross-referencing credential IDs against instance configurations
   - **Orphan reference detection** — valuable for preventing silent auth 
failures when a credential is deleted
   - **Filtering + CSV export** — standard UX patterns, low implementation risk
   - **No secret exposure** — correct security boundary; the inventory should 
only surface metadata (credential name, vendor, status), never 
AccessKey/SecretKey values
   
   **Implementation notes:**
   - The backend needs a new read-only API that joins credential metadata with 
instance configuration data. If instances are paginated, consider a batched 
approach to avoid loading all instances into memory.
   - Vendor mismatch detection requires a consistent vendor enum on both 
credential and instance sides.
   - CSV export should respect the same filter state as the UI table.
   
   This is a good candidate for community contribution.
   
   ---
   *Automated evaluation by github-manager*


-- 
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]

Reply via email to