Expose provider resources through generic HTTP routes #57
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
The server router registers
/api/v1/containersand container-address detail/action routes incrates/server/src/resources.rs:218-230. The server's OpenAPI operation list incrates/server/src/lib.rs:214-227has container handlers and no generic resource-discovery/list/inspect/action route. Default instance recognition incrates/server/src/host_route.rs:120-140is Docker/Podman-specific.Recommendation
Add the generic discovery and resource list/inspect/plan/action surface through
crates/proto, with generated OpenAPI and client output. Keep current Docker/Podman v1 routes and identifiers as compatibility projections; do not widen the closedEngineenum.Payoff and estimate
A provider implementing existing capabilities can be exposed without another container-shaped server branch. Estimate: 2–4 engineering days for route/DTO migration and parity tests; this is part of the 5–10 day vertical slice in the report.
Priority: Next milestone (PLAN step 5).
2026-10-04 owner decisions: Matches first-party provider crates behind one trait and generic schema-driven resource UI. Existing v1 API compatibility remains required. Related: #49.
Report: arch-review report
Source: arch-review 2026-10-04