Releases: daptin/daptin-cli
Releases · daptin/daptin-cli
v0.8.1
v0.8.0
Full Changelog: v0.7.1...v0.8.0
v0.7.1
Full Changelog: v0.7.0...v0.7.1
v0.7.0
Full Changelog: v0.6.1...v0.7.0
v0.6.1
Full Changelog: v0.6.0...v0.6.1
v0.6.0
Full Changelog: v0.5.0...v0.6.0
v0.5.0
What's New
Complete WebSocket pub/sub CLI (#23)
ws listen— stream all events from the server (no topic required)ws subscribe <topic> [topic2 ...]— subscribe to one or more topics with optional--filterws ping— check WebSocket liveness with round-trip latencyws publish <topic> <json>— publish a message to a topicws topic create/delete <name>— manage user topicsws topic permission <name> [--set <value>]— get or set topic permission bitmaskws verify --endpoints a,b— verify cross-node PubSub delivery
Fixes
- Switch WebSocket client from
x/net/websockettogorilla/websocketfor reliable framing - Decode base64 response data from server correctly
- Fix
ws topic permissionget (readdatafield, format as integer) - Add
relate,unrelate,wsto arg reorder for flags-after-args support
Observability
- Structured
log/sloglogging across all code paths --debugflag enables debug-level output (context resolution, WS frames, HTTP requests, config)- Default level: warn (silent for normal use)
Testing
- 9 new WebSocket e2e tests (35 total, all passing)
- Tests sign up unique users per run, verify pub/sub delivery end-to-end
Full Changelog: v0.4.0...v0.5.0
v0.4.0
What's New
WebSocket pub/sub commands (daptin ws)
Full support for Daptin's real-time WebSocket API (/live endpoint):
ws listen <topic>— Subscribe to a topic and stream events as JSON lines. Supports--filter key=valuefor server-side filtering (includingEventType=create|update|delete).ws publish <topic> <json>— Publish a message to a topic.ws topic create|destroy|set-permission— Manage user-created topics.ws verify --endpoints ep1,ep2— Cross-node PubSub health check for cluster deployments. Connects to two endpoints, creates a topic, subscribes, publishes, and verifies delivery with latency measurement.
Improved error reporting
WebSocket connection failures now surface the actual HTTP status code and server response body instead of the opaque "bad status" error.
Example usage
# Stream CRUD events on a table
daptin ws listen user_account
# Stream only create events
daptin ws listen user_account --filter EventType=create
# Publish to a user topic
daptin ws topic create notifications
daptin ws publish notifications '{"text": "hello world"}'
# Verify cluster PubSub
daptin ws verify --endpoints http://pod-0:8080,http://pod-3:8080Full Changelog: v0.3.0...v0.4.0
v0.3.0
Full Changelog: v0.2.1...v0.3.0
v0.2.1
Full Changelog: v0.2.0...v0.2.1