Expose volume claims and VM attachment in the CLI #124

New issue

Open

opened 2026-09-15 06:55:34 +00:00 by a73x · 0 comments

a73x commented

2026-09-15 06:55:34 +00:00

Owner

Part of #122. The HTTP API supports creating, listing, inspecting and deleting volume claims, but the CLI has no volume commands.

Outcome

A tenant can manage a claim and create a VM using it entirely through the CLI.

Acceptance criteria

Add claim create/list/show/delete commands using the existing API.
VM creation accepts multiple claim names or IDs and preserves their order.
Display size, pending/bound state, host, attached VM and presence; unknown presence remains distinct from absent.
Surface tenant, capacity, host-pinning and claim-in-use errors clearly. Explain that attachment currently happens at VM creation and reuse waits for the old VM to be reaped.
Document a create/attach/delete-VM/reuse workflow and verify argument serialization and API failures.

References: docs/volumes.md, internal/server/api/volumes.go, internal/cli.

Part of #122. The HTTP API supports creating, listing, inspecting and deleting volume claims, but the CLI has no volume commands. ## Outcome A tenant can manage a claim and create a VM using it entirely through the CLI. ## Acceptance criteria - Add claim create/list/show/delete commands using the existing API. - VM creation accepts multiple claim names or IDs and preserves their order. - Display size, pending/bound state, host, attached VM and presence; unknown presence remains distinct from absent. - Surface tenant, capacity, host-pinning and claim-in-use errors clearly. Explain that attachment currently happens at VM creation and reuse waits for the old VM to be reaped. - Document a create/attach/delete-VM/reuse workflow and verify argument serialization and API failures. References: docs/volumes.md, internal/server/api/volumes.go, internal/cli.