tuna-cli v0.40.0
Check your inspector settings
In the Docker image, the inspector of tuna http, tuna 1c, and tuna kubernetes is now off; turn it on with TUNA_INSPECT=true. The inspectAddr key in tuna.yml is no longer read, and a busy --inspect-port stops the tunnel. See the inspector page.
- [FEATURE] Adds MySQL protocol handler (cli)
- [FEATURE] Shows rejected requests and policy decisions in the inspector (cli)
- [FEATURE] Adds an inspector API for agents (cli)
- [FEATURE] Lets agents wait for inspector events over HTTP (cli)
- [FEATURE] Moves inspector developer tools to tested Go code (cli)
- [ENHANCEMENT] Adds --inspect-port and turns the inspector off in Docker images (cli)
- [ENHANCEMENT] Links Postgres statements in the inspector and caps history by bytes (cli)
- [ENHANCEMENT] Names MySQL commands in inspector events instead of event codes (cli)
- [ENHANCEMENT] Keeps the tunnel address across reconnects with tunnel sessions (cli)
- [BUGFIX] Switches to another node when the assigned one is unreachable (cli)
- [BUGFIX] Fixes inspector subscribers hanging the tunnel and unsafe replay (cli)
- [BUGFIX] Keeps the browser from showing a stale inspector after a CLI update (cli)
- [BUGFIX] Fixes --rate-limit letting through twice the limit at a window boundary (cli)