Skip to content

docs(readme): warn that a command reading stdin caches empty output (LAB-7735) #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
27Bslash6 merged 1 commit into from
Oct 3, 2026
Merged

docs(readme): warn that a command reading stdin caches empty output (LAB-7735) #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,13 @@ shell. Pass input in arguments, files or `--scope` instead. Programs that
prompt by opening the terminal themselves, as `op`, `ssh` and `sudo` do, still
reach you.

A command that reads its input from stdin, such as `jq`, `envsubst` or
`python3 -`, therefore reads nothing. If it still exits 0, ck caches that
output like any other, with no warning: `curl -s "$URL" | ck run -- jq -r .token`
caches an empty token. To cache a pipeline, wrap the command that produces the
input instead: `ck run --ttl 5m -- curl -s "$URL" | jq -r .token` caches curl's
output and runs `jq` on it every time.

### What the key does not cover

The key is the command and its arguments, plus `--scope`. It does not cover
Expand Down
Loading