pikopod requests

pikopod requests <sandbox> [--last 50] [--scope <token>] [--reset]
pikopod requests <sandbox> --explain <METHOD> <path> [--body <json>] [--auth=false]

The journal

The request journal of a running sandbox: what your code actually sent, newest last.

#1    POST   /charges                                 → 201
#2    GET    /charges/ch_a91f3c                       → 200  (/charges/{id})
2 request(s)

When the bounded journal has evicted older entries, the footer says how many, because ordering claims across the gap cannot be proven. --reset clears the journal. --scope <token> shows, or with --reset clears, only the requests that carried X-Pikopod-Scope: <token>; when any scoped request has been seen, the footer counts live and evicted scopes:

#1    POST   /charges                                 → 503
#2    POST   /charges                                 → 503
#3    POST   /charges                                 → 201
3 request(s) in scope "worker-1" — 2 live scope(s), 0 evicted

See Request journal.

—explain

Replays one request in-process against an ephemeral fork of the sandbox’s current state, with the narrator on. No real state is touched and no server is needed. Deterministic replay means the trace is the truth, not an approximation.

Flag	Meaning
`--body <json>`	A JSON request body.
`--auth`	Send the sandbox’s issued credential. Default true. Pass `--auth=false` to see the refusal path.

pikopod requests examplepay --explain POST /charges --body '{"amount": 1250, "currency": "NGN"}'

replaying POST /charges against a fork of examplepay (seed 1f41d4ff6d02c840) — no real state is touched

  auth       sending the issued credential in authorization
  faults     no armed fault fired
  route      matched createCharge
  auth       declared auth satisfied
  operation  kind=create resource=/charges

→ 201
  Content-Type: application/json; charset=utf-8
  Etag: "0"
  X-Pikopod-Operation: createCharge

{"amount":1250,"currency":"NGN","id":"charges_1","status":"failed"}

pikopod requests examplepay --explain GET /charges --auth=false

  faults     no armed fault fired
  route      matched listCharges
  auth       declared auth REFUSED the request (401) — the issued credential is in `pikopod sandbox list`

→ 401
  Content-Type: application/json; charset=utf-8
  Www-Authenticate: Bearer
  X-Pikopod-Operation: listCharges

{"message":"Authentication required"}

The path must be provider-relative and start with /. Bodies longer than 2000 characters are truncated in the output. The output ends with the same request as a curl line against the running sandbox, with the credential as $PIKOPOD_CREDENTIAL and the base URL as $PIKOPOD_URL:

send the same request to the running sandbox:
  curl -X POST "$PIKOPOD_URL/examplepay/charges" -H "authorization: Bearer $PIKOPOD_CREDENTIAL" -H 'content-type: application/json' --data '{"amount":5000,"currency":"usd"}'

Old spellings

pikopod sandbox requests <sandbox> and pikopod why <sandbox> <METHOD> <path> still work this release. Each prints one line on stderr naming the spelling above.

CLI

Interfaces

Schemas

pikopod requests

The journal

—explain

Old spellings

​The journal

​—explain

​Old spellings

The journal

—explain

Old spellings