macOS
Homebrewverified · 100%
brew install apigeeclilocal Homebrew formula metadata
brew / rank 7073
Install apigeecli with Homebrew
Apigee management API command-line interface. Version 2.17.0 via Homebrew; verified 2026-07-27.
install
Additional install commands
overview
Package summary
Apigee management API command-line interface
Project links
Commands and aliases
- apigeecli
history
Project history and usage
apigeecli is a Go command-line interface for interacting with Apigee APIs across Apigee hybrid and Google's managed Apigee offering. It manages Apigee entities such as proxies, products, environments, developers, IAM, key stores, shared flows, and related control-plane resources.
Project history
The public apigee/apigeecli repository was created in 2022. The README describes it as a tool for Apigee hybrid and managed Apigee, including CRUD-style management of Apigee entities and helper flows for service accounts used by hybrid runtime operations.
GitHub releases show an active release stream beginning with v1.107 in May 2022 and continuing through the 2.x line. The README documents version 2.x breaking flag-name changes and a 2.0.0 change adding --no-warnings for automation-sensitive output.
Adoption history
The README documents binary downloads from GitHub releases, a Linux/Darwin install script, a container image on GitHub Container Registry, Docker usage, and Cloud Build usage. The batch input shows Homebrew packaging, giving macOS users another straightforward installation path.
How it is used
apigeecli authenticates with Google OAuth access tokens from gcloud, metadata tokens in Google execution environments, Google default application credentials, or service account JSON. It can generate and cache access tokens, list or fetch organizations, and run broad Apigee management commands.
The README says token cache and preferences are written under $HOME/.apigeecli. Generated command docs show inherited global options for service-account JSON, metadata token, default token, OAuth token, API environment selection, output control, and newer-version checks.
Why package nerds care
apigeecli is significant as the scriptable control-plane surface for Apigee users who need reproducible API-management operations outside the web console. Package users care about its release cadence, generated Cobra command tree, token-cache location, container image, and CI-friendly flags because it often appears in deployment and platform administration pipelines.
Timeline
- 2022: Public apigee/apigeecli repository created.
- 2022: v1.107 through v1.110 releases published during the first public release wave.
- 2025: 2.x releases continued with monthly feature and fix updates.
- 2026: v2.17.0 published and command docs regenerated on January 5, 2026.
Related projects
- apigeecli is directly tied to Google Cloud Apigee, the Apigee REST APIs, Apigee hybrid, gcloud authentication, Google default application credentials, Cloud Build, and GHCR container distribution.
Sources
- https://api.github.com/repos/apigee/apigeecli
- https://cloud.google.com/apigee/docs/reference/apis/apigee/rest
- https://github.com/apigee/apigeecli#readme
- https://github.com/apigee/apigeecli/blob/main/docs/apigeecli.md
- https://github.com/apigee/apigeecli/blob/main/docs/apigeecli_preferences.md
- https://github.com/apigee/apigeecli/blob/main/docs/apigeecli_token_cache.md
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
~/.apigeecli
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.apigeecli
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
apigeecli | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version2.17.0
manager updated2026-07-27
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:apigeecli |
|---|---|
| Version | 2.17.0 |
| Package manager | Homebrew |
| Homepage | https://cloud.google.com/apigee/docs |
| Repository | https://github.com/apigee/apigeecli |
| Last updated | 2026-07-27T09:29:36-04:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- pkg.so package database
- pkgdb category and tag curation