From b424a80b06dfd103b7b150ce9c7de2194df9de93 Mon Sep 17 00:00:00 2001 From: CMGS Date: Thu, 3 Sep 2026 00:00:01 +0800 Subject: [PATCH] docs: name the RPCs without a command and say where --limit applies The README claimed every core RPC has a command; five do not. The workload list --limit help said only 'limit data size': the cap is applied by the server before the client-side pod and IP filters, so a filtered list can return fewer rows than the limit. --- README.md | 3 ++- cmd/workload/cmd.go | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c28b896..3eab1c7 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,8 @@ pods, nodes, workloads, images, networks and one-shot lambdas. ## Highlights - Eight command groups — `core`, `pod`, `node`, `workload`, `image`, `network`, `status`, `lambda` — - covering every RPC eru core exposes. + covering eru core's RPCs; `GetPod`, `GetWorkload`, `GetNodeStatus`, `GetNodeEngineInfo` and + `RawEngine` have no command of their own. - Table, JSON or YAML output for every read command, selected once with `--output`. - Interactive streams: `workload exec` and `lambda` attach a raw terminal, forward `SIGWINCH` and return the remote exit code as their own. diff --git a/cmd/workload/cmd.go b/cmd/workload/cmd.go index 02f9c7c..0bcf801 100644 --- a/cmd/workload/cmd.go +++ b/cmd/workload/cmd.go @@ -128,7 +128,7 @@ func Command() *cli.Command { }, &cli.Int64Flag{ Name: "limit", - Usage: "limit data size", + Usage: "cap the rows the server returns; --pod, --match-ip and --skip-ip then filter on the client, so fewer rows can come back", }, &cli.StringSliceFlag{ Name: "match-ip",