playbooks

home / skills / openclaw / skills / azion-deploy

azion-deploy skill

/skills/askrauthein/azion-deploy

This skill deploys projects to Azion via Azion CLI with preflight checks to verify auth and manifest presence.

npx playbooks add skill openclaw/skills --skill azion-deploy

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
1.6 KB
---
name: azion-deploy
description: Deploy applications, static sites, and edge functions to Azion using Azion CLI. Use when the user asks to deploy/publish to Azion, configure link/build/deploy flow, or troubleshoot Azion auth/project linking problems.
version: 0.1.1
author: AskClaw
entrypoint: scripts/azion-deploy.sh
metadata: {"openclaw":{"emoji":"🚀","short":"Deploy to Azion (CLI)","requires":{"bins":["bash","azion"]}}}
user-invocable: true
command-dispatch: tool
command-tool: azion-deploy
commands:
  - name: azion-deploy
    usage: azion-deploy <preflight|auth-check|quickstart|deploy-local> [args]
    description: Deploy helper wrapper around azion CLI with preflight/auth checks.
---
# azion-deploy

Use this skill to deploy projects to Azion with safe preflight checks.

## Built-in checks

The script fails fast if:
- `azion` executable is missing
- authentication fails (`azion whoami`)
- `.edge/manifest.json` is missing when using `--skip-build`

## Commands

```bash
# Validate CLI + auth
bash {baseDir}/scripts/azion-deploy.sh preflight

# Validate auth only
bash {baseDir}/scripts/azion-deploy.sh auth-check

# Stable quickstart flow
bash {baseDir}/scripts/azion-deploy.sh quickstart --name <project-name> [--token "$AZION_TOKEN"]

# Local deploy flow
bash {baseDir}/scripts/azion-deploy.sh deploy-local [--skip-build] [--auto] [--token "$AZION_TOKEN"]
```

## Notes

- Keep `link -> build -> deploy` sequential (never parallel).
- If `whoami` fails, run `azion login` (interactive) or provide valid `AZION_TOKEN`.
- For detailed flags and framework behavior, read:
  - `references/azion-cli.md`
  - `references/azion-build-frameworks.md`

Overview

This skill deploys applications, static sites, and edge functions to Azion using the Azion CLI with safe preflight checks. It automates auth validation, optional build steps, and sequential link → build → deploy flows to reduce mistakes. Use it to run validated, repeatable deployments from local scripts or CI pipelines.

How this skill works

The skill wraps azion CLI commands and performs built-in checks before taking action. It verifies the azion executable is available, confirms authentication (azion whoami), and ensures required artifacts like .edge/manifest.json exist when skipping the build. Commands expose preflight, auth-check, quickstart, and deploy-local flows with flags for tokens, skip-build, and automation.

When to use it

  • You want to publish a static site, edge function, or application to Azion.
  • You need to validate Azion CLI presence and authentication before CI/CD deploys.
  • You want a repeatable quickstart flow to link, build, and deploy a project.
  • You need a local deploy flow that can skip build or run unattended in automation.
  • You are troubleshooting project linking or token/auth issues with Azion.

Best practices

  • Always run the preflight check before deployment to catch missing CLI or auth issues early.
  • Keep link → build → deploy sequential; never run those steps in parallel to avoid inconsistent state.
  • Prefer AZION_TOKEN for non-interactive environments; use azion login for interactive sessions.
  • When using --skip-build, ensure .edge/manifest.json is present and up to date.
  • Use auth-check in CI to fail fast if credentials are invalid or expired.

Example use cases

  • Run preflight in a CI job to validate CLI and credentials before expensive build steps.
  • Use quickstart to create and publish a named project with a single command during onboarding.
  • Perform deploy-local --skip-build in a staging environment when build artifacts are produced elsewhere.
  • Add auth-check as a pipeline gate to ensure AZION_TOKEN is valid before deployment.
  • Troubleshoot failed whoami responses by prompting an interactive azion login or rotating the token.

FAQ

What fails the preflight checks?

Preflight fails if the azion executable is missing, authentication (azion whoami) fails, or required artifacts like .edge/manifest.json are missing when using --skip-build.

How do I run non-interactive deployments?

Provide a valid AZION_TOKEN environment variable to the script or pass --token "$AZION_TOKEN"; this avoids interactive azion login prompts.