Remove resource pools, leases and wait queues

Drop the resource allocation feature end to end: store tables and migration, runner scheduling and cleanup, protocol types and commands, CLI commands, TUI screens, tests and docs. Existing databases open cleanly and definitions carrying a retired resources block still validate.
This commit is contained in:
2026-10-19 22:27:27 +01:00
parent a676b30ff0
commit 72aecd8b1f
45 changed files with 282 additions and 3954 deletions
-15
View File
@@ -16,21 +16,6 @@ service manager directly. Legacy Python-managed installations require an explici
For source development, use `go run ./cmd/pipelines help`; start the native server
separately. Set `PIPELINES_URL` or pass `--url` to select another server.
## Local resource pools
`pipelines resource-pool-inspect NAME --json` reads a declared pool's members,
enabled/quarantined status and non-secret metadata. It does not report lease tokens.
`pipelines resource-pool-configure pool.json --yes --json` replaces the full pool
declaration; use `-` instead of a file to read stdin. Input is limited to 256 KiB.
Without `--yes`, interactive confirmation is required. Both commands require the
loopback operator transport; ordinary remote/stage clients are refused.
Declarations contain `name` and `members`, each with `member`, `enabled`, optional
`quarantined` and bounded string `metadata`. Existing validation limits the member
count to 32 and metadata to 16 fields per member. Configuration does not release
active owners, discard waiters or prove a device is ready; inspect ownership and
verify readiness before activating a target. Never put credentials in metadata.
## Dashboard and status
`pipelines --url ws://HOST:PORT/connect ping --json` returns `pong` with the