mengw15 opened a new pull request, #7819: URL: https://github.com/apache/texera/pull/7819
### What changes were proposed in this PR? The dashboard page for managing per-user warehouses, mirroring the computing-unit tab's structure and look: a `user-warehouse` container with virtual-scroll row cards (`user-warehouse-list-item`, hover actions, same row anatomy and heights as computing units), a shared create modal, a read-only details dialog (name, owner, flavor, created), and a `cloud-server` sidebar entry gated on the deployment's `warehouseEnabled`. Plumbing shared with the upcoming picker (#7817): `warehouse.service.ts` (status/create/delete plus the execution-time pick it will consume) and `WarehouseActionsService`, which owns the delete confirmation and keeps the dialog busy until the backend finishes waiting out Lakekeeper's asynchronous purge (#7742). With the flag off (every deployment today) the UI is unchanged. ### Any related issues, documentation, discussions? Closes #6933. Part of #6870; the on-canvas picker follows in #7817. ### How was this PR tested? - Vitest specs for every new piece: tab container, list item, create modal, details dialog, HTTP service, and actions service (51 tests across 7 files, run against this branch's tree alone); failure paths verified by breaking the code and watching the specs go red. - Manual end-to-end on a local deployment with the flag on: create/list/delete against live Lakekeeper + MinIO, including deleting a warehouse that held execution data. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (claude-fable-5, claude-opus-5) -- 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]
