Add clickable VM overview pages with primary lifecycle actions #17
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User requests clickable VM names leading to a dedicated, polished overview with all available instance details and primary Soft Restart, Hard Restart, Shut Off and Reset buttons. Reuse domain/detail loading and existing validated action dialogs; keep selection, connection and refresh states scoped. Reset semantics have been asked explicitly because hard reset, admin reset-state and rebuild differ. Continue console SPICE compatibility work in #16. Verify navigation, loading/error states and action bindings in the browser without touching real cloud resources.
Implemented and pushed in
59d3fa2.Clicking a VM name or details icon opens a dedicated responsive overview with status, task/power/lock state, CPU/RAM/flavor disk, IDs, zone, creation time, IP addresses, security groups/rules, image/key pair, attached volumes and metadata. Metadata is read on demand and never persisted. Inventory publication changes refresh details; Back retains table filters/page.
Primary controls: Soft Restart, Hard Restart, Shut Off (Start when stopped), Reset, Console. The user explicitly confirmed Reset means the same hard reboot as Hard Restart. All controls reuse existing state guards, confirmation dialogs and fresh write preflight. Distinct preparation jobs are serialized to avoid competing with metadata inspection.
Validated browser navigation, detail sections, action mappings without mutation on initial click, locked/busy guards, refresh/back, light/dark and 960/640px layouts. SDK integration passed read-only inspection of locked/busy VM, 128 grouped metadata entries, task/power projection and no metadata values in SQLite. Existing 34 SDK/HTTPS VM workflows and cache/queue regressions passed. Svelte check: zero errors/warnings; production frontend build and worker source/manifest checks passed. No native desktop build/live-cloud acceptance claimed (see #10).