Inventory data view in datumctl

[ecv]

Sub-issue of datum-cloud/tmp_datum-cloud_enhancements_713_Physical-inventory-f_2138d0c1#1 — Physical inventory for Milo, follow-on to datum-cloud/infra#2675.

Goal

A datumctl data view over the inventory service so operators can read the fleet from the CLI — providers, regions, sites, clusters, nodes (and later networkdevices) — against the inventory.miloapis.com/v1alpha1 CRDs now populated on prod.

Today the only way to view loaded inventory is raw datumctl get sites -L topology.inventory.miloapis.com/region (works, but bare). This issue is the first purpose-built read experience.

Context

Real data is loaded on prod (#2675): 4 providers, 18 regions, 19 sites (#2677), 18 clusters, 90 nodes from Omni (#2680). This view consumes that.

Scope

• Commands to list/get inventory kinds with sensible default columns (e.g. site → region, provider, ISO_ID; cluster → site, node count).
• Surface topology.inventory.miloapis.com/* topology labels and key cross-refs (providerRef/regionRef/siteRef) in output.
• Filtering by region/provider/site; -o json|yaml|wide parity with existing datumctl get.
• Read-only.

Open questions

• Dedicated datumctl inventory ... subtree vs. relying on generic datumctl get <kind> with improved column printers.
• Rollup views (e.g. nodes-per-site, sites-per-region) in-CLI vs. deferred to the portal.

Exit criteria

• Operator can list providers/regions/sites/clusters/nodes from datumctl with readable default columns.
• Topology labels + cross-refs visible without -o yaml spelunking.
• Filter by region/provider/site.

Relates

• Sibling: staff-portal inventory view (separate issue).
• Data loaded by datum-cloud/infra#2675.

[ecv]

Pivoted: per @scotwells' review on #212, the inventory view should not bake into datumctl core. It's now a datumctl plugin (datumctl inventory ...) living in the inventory service — milo-os/inventory#41.

Same surface (providers/regions/sites/clusters/nodes lists with filters, tree, summary, -o table/json/yaml), but using the inventory repo's own typed API and the go.datum.net/datumctl/plugin SDK. datumctl#212 closed; no core changes needed. Verified against prod.

Remaining for full closure: release wiring (goreleaser + checksums + listing in datumctl-plugins) so datumctl plugin install works.

[ecv]

Update: the plugin now lives in its own Datum repo — datum-cloud/inventory (https://github.com/datum-cloud/inventory) — not milo-os/inventory. Reason: every other datumctl plugin lives under datum-cloud (e.g. datum-cloud/compute → datumctl-compute); putting a Datum CLI surface in a milo repo crossed the datum/milo boundary. The new repo depends on go.miloapis.com/inventory/api as an external module.

• Install: datumctl plugin install datum-cloud/inventory
• feat(cli): add datumctl-inventory plugin milo-os/inventory#41 closed (superseded); Release wiring for datumctl-inventory plugin (goreleaser) milo-os/inventory#42 closed (release wiring moved)
• Remaining for full closure: cut a release tag, then list in datum-cloud/datumctl-plugins for datumctl plugin install inventory by short name.