Installer aiven-client avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• avn

Historique du projet

The public GitHub repository was created in December 2015, fitting Aiven's early period of exposing its managed-service platform through APIs and automation tooling. The README describes `aiven-client (avn)` as the official command-line client for Aiven and positions it beside the backend service rather than as a third-party wrapper.

The project remained a Python CLI with a small Unix-friendly surface: install from PyPI or Homebrew, authenticate once, then drive Aiven resources through commands that can emit raw REST API JSON for use with tools such as `jq`.

Historique d'adoption

Adoption is mainly tied to Aiven customers and operators rather than to a general-purpose developer audience. Official docs document pip and Homebrew installation, and the Homebrew formula appears in the input package-manager facts as `brew:aiven-client`.

The tool's durable package-manager value is that it gives Homebrew users a first-party `avn` binary without needing to remember Python packaging details, while still staying aligned with the PyPI package and the upstream Aiven API.

Modes d'utilisation

Typical use starts with `avn user login`, either with a username/password flow or an access token generated in the Aiven Console. The client can also read an auth token from `~/.config/aiven/aiven-credentials.json` and a default project from `~/.config/aiven/aiven-client.json`.

The CLI is used for project selection, cloud-region listing, service management, event inspection, access-token management, and automation scripts. Its `--json` output is explicitly documented for piping REST API responses into other command-line tools.

Pourquoi les passionnés de paquets s'y intéressent

For package-manager users, `aiven-client` is a classic vendor CLI formula: the package is not interesting because it is a new language runtime, but because it pins a first-party cloud API surface into reproducible local tooling.

The split between PyPI, uvx, and Homebrew also makes it a useful example of a Python command-line package that needs to feel native in several installer cultures while preserving one executable name, `avn`.

Chronologie

• 2015: Public GitHub repository created for `aiven/aiven-client`.
• Later: Official docs document PyPI, uvx, and Homebrew installation paths.
• 2026: Official docs still present the Aiven CLI as the scriptable command-line interface for the Aiven platform.

Related projects

• Aiven API: the REST API surface that the CLI exposes for shell usage.
• Aiven MCP: a newer official Aiven tool documented alongside the CLI for natural-language management of Aiven services.

Sources

• https://aiven.io/docs/tools/cli
• https://api.github.com/repos/aiven/aiven-client
• https://github.com/aiven/aiven-client
• input source_facts.package-manager.brew