Add generic resource tools and capability-driven UI #64
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?
Problem and evidence
Product clients still encode container vocabulary:
crates/infraternal/src/cli.rs:24-56has a Docker/Podman engine filter,crates/infraternal/src/mcp.rs:677-709exposeslist_containers, andpackages/web/src/lib/inventory.ts:42-82calls only container routes and parses container addresses. This means a provider with existing shared capabilities still needs new product-specific branches.Recommendation
After the generic resource API lands, add generic resource CLI/MCP commands and a shared web summary/detail view driven by effective capabilities. Keep static container commands as aliases. Add the test-only
servicekind acceptance case from the report: List and Inspect only, opaque IDs with slash/percent, no Logs/Exec controls or dispatch, embedded and mTLS routes, exact permission filters, and unchanged v1 Docker/Podman behavior.Payoff and estimate
A provider implementing an existing capability needs registration/adapter tests rather than new branches in four product layers. Estimate: 5–10 engineering days across the generic API and client vertical slice.
Priority: Next milestone (PLAN steps 5–6, after DTOs are stable).
2026-10-04 owner decisions: Matches compiled-in providers behind one trait and the generic schema-driven UI. The design system and current bounded shared tables remain the base. Related: #49.
Report: arch-review report
Source: arch-review 2026-10-04