apigee-cli
!!! Please note that this project was created to help previous Darumatic clients and will no longer be actively maintained. !!!
apigee-cli is a command-line interface tool designed to simplify the use of the Apigee Edge Management API. It provides a user-friendly experience with features such as SSO support. While Google or Apigee does not officially support the tool, it can be used for general administrative tasks, as a developer package, and to support automation for common development tasks such as CI/CD. With the apigee-cli, you can manage your Apigee Edge credentials using environment variables, config files, or command-line arguments. The tool is highly experimental and is not affiliated with Apigee or Google. For more information on getting started with the apigee-cli or for troubleshooting help, refer to the documentation and links provided.
Installation
The easiest way to install apigee-cli is to use pip in a virtualenv:
$ pip install apigeecli
or, if you are not installing in a virtualenv, to install globally:
$ sudo pip install apigeecli
or for your user:
$ pip install --user apigeecli
If you have the apigee-cli installed and want to upgrade to the latest version you can run:
$ pip install --upgrade apigeecli
Getting Started
Before using apigee-cli, you need to tell it about your Apigee Edge credentials. You can do this in three ways:
Environment variables
Config file
Command-line arguments
The steps below show how to use command-line arguments to configure your Apigee Edge credentials.
Basic authentication
$ apigee configure -P default -u MY_EMAIL -p MY_PASS -o MY_ORG -mfa '' -z '' --no-token --prefix ''
Multi-factor authentication (MFA)
$ apigee configure -P default -u MY_EMAIL -p MY_PASS -o MY_ORG -mfa MY_KEY -z '' --no-token --prefix ''
SSO authentication
$ apigee configure -P default -u MY_EMAIL -p none -o MY_ORG -mfa '' -z MY_ZONENAME --no-token --prefix ''
If you are not currently signed in by your identity provider, you will be prompted to sign in:
$ apigee apis list
SSO authorization page has automatically been opened in your default browser.
Follow the instructions in the browser to complete this authorization request.
If your browser did not automatically open, go to the following URL and sign in:
https://{zoneName}.login.apigee.com/passcode
then copy the Temporary Authentication Code.
Please enter the Temporary Authentication Code:
zoneName will be the Identity zone name you previously configured.
Refer to the official Apigee documentation to learn more about how to Access the Edge API with SAML.
Testing your credentials
Run the following command to get a list of API proxies in your default Apigee organization:
$ apigee apis list ["helloworld", "oauth"]
Why does this exist?
It is intended for general administrative use from your shell, as a package for developers, and to support automation for common development tasks, such as test automation or Continuous Integration/Continuous Deployment (CI/CD).
When to use this over the official tool
Apigee Corporation maintains their own fully-featured CLI for the Apigee Management API that can be used as an SDK to orchestrate tasks and may be more than suitable for your needs.
Our Apigee CLI provides a simpler command-line experience with CI/CD and SSO features in mind.
We built and use the Apigee CLI to implement and distribute features that allow our clients to manage CI/CD, perform self-service operations and promote our DevOps workflows which are difficult to perform using official tools.
Getting Help
More Links
For further questions, feel free to contact us at hello@darumatic.com.
Disclaimer
This is not an officially supported Google product.
Metadata
Release files for apigeecli 0.52.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| apigeecli-0.52.0.tar.gz | 65.1 kB | Without provenance | Details for apigeecli-0.52.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| apigeecli-0.52.0-py3-none-any.whl | Python 3 | none | any | Details for apigeecli-0.52.0-py3-none-any.whl |
Total release size: 153.2 kB
Release files / apigeecli-0.52.0.tar.gz
| Download URL | apigeecli-0.52.0.tar.gz |
|---|---|
| Size | 65.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a87917ccda450f2d237e1aa7c1dc1919c0689c2cbe0e2ab320a85801b7805c4d
|
|
BLAKE2b-256 checksum How to use checksums |
b7b0d9509ce23374d4b940e677f0adde5b8c66024217b7e88f70617f3da32d4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / apigeecli-0.52.0-py3-none-any.whl
| Download URL | apigeecli-0.52.0-py3-none-any.whl |
|---|---|
| Size | 88.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f16b903b347e2bb6a1729dc16ef544d36ce246c0bd4f492d3af65397f6e541c9
|
|
BLAKE2b-256 checksum How to use checksums |
d67693249393acc56e95b81146f11bb163fb94a7668ceb8fa8f18e0fb39e971a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for apigeecli 0.52.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.