The aiven-client library provides both a command-line client (`avn`) and a Python API for interacting with Aiven.io services. It's actively maintained with frequent minor releases, currently at version 4.13.0, introducing new features and deprecating older ones regularly.
pip install aiven-clientVerified import paths — ran on the pinned version, not inferred.
Initialize the AivenClient using an API token from an environment variable and list your Aiven projects.
Upgrade your Python interpreter to 3.10 or later.
Migrate to using application users and permissions for managing access, as `teams` functionality is no longer available. Refer to Aiven documentation for current access management practices.
Upgrade your Python interpreter to 3.9 or later. For current versions, use 3.10+.
If you relied on `aiven-client` for InfluxDB management, this functionality is no longer present. Consider alternative methods or Aiven Console for managing existing InfluxDB services.
Review your code for any Redis-specific API calls. Adapt to Valkey-compatible methods and terminology. Existing Redis services were automatically migrated to Valkey.
Always provide a valid Aiven API token during client initialization. It's recommended to load this from environment variables (e.g., `AIVEN_TOKEN`) or a secure configuration system.
Install the library using `pip install aiven-client`. Ensure you are running your script with the Python interpreter where the library was installed.
Set the `AIVEN_TOKEN` environment variable with your Aiven API token before running your script, or pass a valid `auth_token` directly to the `AivenClient` constructor.
Refer to the Aiven documentation for current methods of managing user access and permissions, which no longer involve 'teams' functionality programmatically in the client library.
No dependency data recorded yet.