Argo CD
Give the Sazabi agent the Argo CD CLI (argocd) in its sandbox to inspect application sync status, health, and rollouts.
About
This CLI connection makes the Argo CD CLI (argocd) available in the Sazabi agent's sandbox. The agent can inspect application sync status, health, and rollouts in your Argo CD instance. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.
Prerequisites
- A Sazabi project.
- An Argo CD server URL (
ARGOCD_SERVER) and an Argo CD authentication token (ARGOCD_AUTH_TOKEN).
Set up in the dashboard
Configure the sandbox in the dashboard under Settings > Sandbox CLIs.
Find Argo CD in the catalog
In Settings > Sandbox CLIs, find Argo CD under Browse sandbox CLIs and choose to connect it.
Provide credentials
Enter the required values: ARGOCD_SERVER — the hostname of your Argo CD API server (for example argocd.example.com); ARGOCD_AUTH_TOKEN — an Argo CD API token. 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 Argo CD CLI connection with the Sazabi CLI (installed and authenticated — see CLI reference).
sazabi sandbox-clis set --type argocd --env ARGOCD_SERVER=<your-argocd-host> --env ARGOCD_AUTH_TOKEN=<your-argocd-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 argocd CLI (for example argocd app list) 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 Argo CD 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 argocd.