01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 rotator check02What you get
Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.
$ p202 rotator check id name reason status -- ---------------------- ------ ------ 1 SaaS pricing geo split OK
$ p202 rotator check --json { "data": [ { "id": 1, "name": "SaaS pricing geo split", "reason": "", "status": "OK" } ] }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 rotator checkSet flags below; the command updates as you type.
04How it works
Exits non-zero if any checked rotator has a configuration problem, so it can gate a deploy.
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands rotator check --json. - With
AI_AGENT,CLAUDECODEor another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with ahint. - Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
{
"path": "p202 rotator check",
"use": "check [rotator_id]",
"short": "Health-check rotators: flag missing defaults, ruleless rotators, empty rules",
"long": "Exits non-zero if any checked rotator has a configuration problem, so it can gate a deploy.",
"runnable": true
}