CLI reference
| Command | What it does |
|---|---|
pulse server start --dev | Boot a local Pulse and auto-login the CLI |
pulse new <app> --source … --stage <engine>:<name> [--sink …] | Scaffold pulse.yaml + sample.json + README |
pulse new --list-sources / --list-sinks / --list-operators / --list-templates | Explore the palette |
pulse new <app> --from-template <id> | Materialize a template into a plain pulse.yaml |
pulse deploy . | Deploy the app: source, stages, sink, API + SDK |
pulse events publish --topic <t> --value @f.json | Publish a test event |
pulse events tail --topic <t> | Live-tail any topic |
pulse logs -f | Tail the engine log |
pulse metrics agent <name> | Per-agent throughput, lag, errors |
pulse secret set <NAME> <value> | Store a secret for ${secret:NAME} |
pulse secret list / rm <NAME> / path | Manage the local secret store |
The stage chain rule: stage n consumes stage n−1's topic and publishes to <app>.<stage>.out. The app ingress topic is <app>.in.