CNS-145 - Flatten data for Cluster Usage table - #38437
Conversation
…o one row per replica, with an added cluster name column. A cluster with 2 replica now displays 2 rows. A cluster with 0 replicas in displayed with dashes in most columns.
QA LLM Review1. MEDIUM -- Give the flattened rows stable IDs
The flattened table relies on position-based row IDs while every replica row owns stateful Alter and Drop dialogs. A live replica insertion or removal can therefore reuse an open dialog component for a different cluster, so submitting the dialog can alter the wrong cluster. DetailsNo |
Motivation
Feedback from Product team and others indicated that the previous design, grouped rows that separated out clusters and their replicas, should be simplified. This has an added benefit of reducing complexity in the UI code, which should make it easier to build out forthcoming enhancements.
Description
Simplify Cluster Replica Usage table by flattening the data to one row per replica, with an added cluster name column. A cluster with 2 replica now displays 2 rows. A cluster with 0 replicas in displayed with dashes in most columns.
Verification
Revised automated tests to handle single rows. Verified behavior locally. This version of the table is still gated behind a feature flag, so this PR does not touch any production-visible code.