From zeabur
Updates Zeabur service environment variables, restarts services, or changes image tags without full redeploy. Use for fixing config, adding vars, or version upgrades.
npx claudepluginhub zeabur/agent-skills --plugin zeaburThis skill uses the workspace's default tool permissions.
> **Always use `npx zeabur@latest` to invoke Zeabur CLI.** Never use `zeabur` directly or any other installation method. If `npx` is not available, install Node.js first.
Manages Zeabur service environment variables via CLI: create, update, delete, list, import from .env, and troubleshoot empty vars, shell expansion, SERVICE_NOT_FOUND.
Manages environment variables handler operations in DevOps basics, providing step-by-step guidance, best practices, and configurations for git, docker, CI/CD, infrastructure fundamentals.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Always use
npx zeabur@latestto invoke Zeabur CLI. Never usezeaburdirectly or any other installation method. Ifnpxis not available, install Node.js first.
# 1. Get service ID (use the `zeabur-service-list` skill)
npx zeabur@latest service list --project-id <project-id> -i=false
# 2. Check current variables
npx zeabur@latest variable list --id <service-id> -i=false
# 3a. Add new variables (errors if key already exists)
npx zeabur@latest variable create --id <service-id> \
--key "KEY1=value1" \
--key "KEY2=value2" \
-i=false -y
# 3b. Update existing variables (only updates specified keys)
npx zeabur@latest variable update --id <service-id> \
--key "KEY1=new_value1" \
-i=false -y
# 4. Restart service (use the `zeabur-restart` skill for details)
npx zeabur@latest service restart --id <service-id> -y -i=false
| Issue | Solution |
|---|---|
${VAR} references | Set in Dashboard, not CLI (shell expands to empty) |
For prebuilt/marketplace services, update the image tag to switch versions.
This is the ONLY correct path for version upgrades or downgrades. Do NOT use
zeabur-deploy(or any redeploy / delete-and-recreate flow) as a substitute — those flows can orphan or wipe the service's mounted disk. A tag update triggers a clean redeploy with the new image while the volume stays attached.
# 1. Get service ID (use the `zeabur-service-list` skill)
npx zeabur@latest service list --project-id <project-id> -i=false
# 2. Update tag (triggers redeploy automatically)
npx zeabur@latest service update tag --id <service-id> -t <new-tag> -y -i=false
| Flag | Description |
|---|---|
--id | Service ID (required, do not use --name) |
-t, --tag | New image tag to deploy |
--env-id | Environment ID (optional, resolved automatically) |
-y, --yes | Skip confirmation |
Note: Updating the tag triggers a new deployment. The service will restart with the updated image.