Aiven
Give the Sazabi agent the Aiven CLI (avn) in its sandbox to manage Aiven services and projects.
About
This CLI connection makes the Aiven CLI (avn) available in the Sazabi agent's sandbox. The agent can manage Aiven services and projects on your behalf. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- An Aiven authentication token (
AIVEN_AUTH_TOKEN).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Aiven in the catalog
In Settings > Sandbox CLIs, find Aiven under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required values: AIVEN_AUTH_TOKEN — your Aiven personal authentication token. Optionally set AIVEN_PROJECT to scope commands to a default project. Save to store them securely; Sazabi injects them into the sandbox when the agent runs.
Set up with the CLI
You can also configure the Aiven CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type aiven --env AIVEN_AUTH_TOKEN=<your-aiven-token>To validate the credentials without saving, run the same command with test in place of set (the test command also requires the --env flags).
Verify
Ask the agent, in a thread, to run the avn CLI (for example avn user info) and confirm it returns real output from your account. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated, recheck the credentials.
Troubleshooting
Command not found — Confirm the Aiven CLI connection is enabled for the project under Settings > Sandbox CLIs.
Authentication fails — Recheck the credential values; a rotated or revoked token must be re-entered under Settings > Sandbox CLIs or with sazabi sandbox-clis set --type aiven.