awa-cli
Command-line interface for the Awa Postgres-native job queue. Run migrations, inspect and manage jobs, walk the storage transition, drive the Dead Letter Queue, list cron schedules, and serve the web admin UI.
Install
The CLI is shipped as both a Rust binary and a Python wheel. Either distribution gives you the same awa executable, including the embedded React admin dashboard for awa serve.
# Python (no Rust toolchain needed)
pip install awa-cli
# Rust
cargo install awa-cli
If you're already using the awa-pg Python SDK, install both with one command:
pip install 'awa-pg[ui]'
That pulls in awa-cli as a dependency so python -m awa serve works end-to-end alongside the worker SDK.
Quick start
# Run migrations
awa --database-url $DATABASE_URL migrate
# Inspect
awa --database-url $DATABASE_URL queue stats
awa --database-url $DATABASE_URL job list --state failed
awa --database-url $DATABASE_URL job dump 12345
awa --database-url $DATABASE_URL job dump-run 12345
# Admin
awa --database-url $DATABASE_URL job retry 12345
awa --database-url $DATABASE_URL queue pause email
awa --database-url $DATABASE_URL queue drain email
# Web UI
awa --database-url $DATABASE_URL serve
# → http://127.0.0.1:3000
DATABASE_URL may be passed as the --database-url flag or read from the environment.
Commands
| Command | Description |
|---|---|
migrate |
Apply migrations, or extract / print SQL with --sql / --extract-to |
job list |
List jobs with --state / --kind / --queue filters |
job dump <id> |
Pretty-print one job and its full lifecycle metadata |
job dump-run <id> [--attempt N] |
Pretty-print one attempt run |
job retry <id> |
Retry a failed or cancelled job |
job cancel <id> |
Cancel a job |
job retry-failed (--kind K | --queue Q) |
Retry every failed job matching exactly one filter |
job discard --kind K |
Delete every failed job of a given kind |
queue stats |
Per-queue depth, lag, and throughput |
queue pause / resume / drain <queue> |
Queue admin |
cron list / remove |
List or remove cron schedules |
dlq depth [--queue Q] |
Total DLQ rows, optionally split by queue |
dlq list |
List DLQ entries with --kind / --queue / --tag / --before-* filters |
dlq retry <id> |
Retry a single DLQ row |
dlq retry-bulk |
Retry every DLQ row matching the filter (--all required if no filter is given) |
dlq move |
Move existing failed terminal rows into the DLQ |
dlq purge |
Delete DLQ rows matching the filter (--all required if no filter is given) |
storage status |
Current storage-transition state |
storage prepare --engine E |
Prepare a future storage engine without changing routing |
storage prepare-queue-storage-schema |
Materialize the queue-storage schema (tables, indexes, functions) |
storage enter-mixed-transition |
Begin routing new writes to the prepared engine |
storage finalize |
Finalize the transition once drain and capability gates pass |
storage abort |
Abort a prepared or mixed-transition rollout |
serve |
Start the embedded web admin UI |
Run awa <command> --help for the flags on any subcommand.
Storage transition
For an existing 0.5.x cluster moving to the queue-storage engine, the typical sequence is:
awa --database-url $DATABASE_URL storage prepare-queue-storage-schema
awa --database-url $DATABASE_URL storage prepare --engine queue_storage
# ... roll out a binary that supports queue storage to all workers ...
awa --database-url $DATABASE_URL storage enter-mixed-transition
# ... drain the canonical engine ...
awa --database-url $DATABASE_URL storage finalize
See docs/upgrade-0.5-to-0.6.md for the full pre-flight checklist, gate semantics, and rollback notes. Fresh installs auto-finalize on first migrate and do not need this sequence.
Dead Letter Queue
dlq retry-bulk and dlq purge require an explicit filter (--kind, --queue, or --tag) or --all. This is intentional — a bare bulk retry / purge with no filter would touch every DLQ row, which is almost never what you want. See docs/dead-letter-queue.md.
Web UI
awa serve starts an embedded admin UI (awa-ui) bound to 127.0.0.1:3000 by default. The UI is read-only when the database reports transaction_read_only = on (e.g. on a replica) or when --read-only is passed explicitly. Mutation endpoints return 503 in that mode.
License
MIT OR Apache-2.0
1 maintainer
Release files for awa-cli 0.6.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| awa_cli-0.6.6-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| awa_cli-0.6.6-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| awa_cli-0.6.6-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| awa_cli-0.6.6-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 21.5 MB
Release files / awa_cli-0.6.6-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | awa_cli-0.6.6-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
c167df42ce1d5722451990863c11efa2e243084609ce204a73870cc3a105e9be
|
|
BLAKE2b-256 checksum How to use checksums |
6b8c7dacb5d156571b4a276e56275cb4aabbe4477bc51466d1c59d810fd3f7f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / awa_cli-0.6.6-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | awa_cli-0.6.6-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
962bc24301b906eb7918a9db08ea0aaa70c581c25ccd7c11260b6c91cb29dd26
|
|
BLAKE2b-256 checksum How to use checksums |
af794692d801475828afd3280be76060c7e9efa9b96408b28016695e58f13cac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / awa_cli-0.6.6-py3-none-macosx_11_0_arm64.whl
| Download URL | awa_cli-0.6.6-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.2 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
67b5a2d66792a45bf4b9e47e62423cc58af62a7333864dac960ceef62f834590
|
|
BLAKE2b-256 checksum How to use checksums |
c1f7869ab08281ec8b8e2fb3f569701f20f5328f70c87035d99cda477ba7ff31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / awa_cli-0.6.6-py3-none-macosx_10_12_x86_64.whl
| Download URL | awa_cli-0.6.6-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
0f267aaaa44a6422f74879dcb02b4763bb56df888f586c3b293b5560088f41f3
|
|
BLAKE2b-256 checksum How to use checksums |
51c2bc713debc7e6c7b34e6fdce82d01f9bb7df6c7390a9c5a898397a6e4a3e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency log
