What is the Agave Platform?
The Agave Platform is an open Science-as-a-Service platform that empowers users to run code, manage data, collaborate meaningfully, and integrate easily with the world around them.
For more information, visit the Agave Developer’s Portal.
What is the Agave CLI
The Agave command line interface (CLI) is a collection of Bash shell scripts allowing you to interact with the Agave Platform. The CLI allows you to streamline common interactions with the API and automating repetitive and/or background tasks.
Installation from source
The following dependencies are required to use the Agave API cli tools.
* bash 4.2.50+ * curl 7.19.7+
* jq 1.4+ (for faster JSON parsing) * python 2.7.9+
Clone the repository from Bitbucket and add the bin directory to your PATH and you're ready to go.
git clone https://bitbucket.org/agaveapi/cli.git agave-cli export PATH=$PATH:`pwd`/agave-cli/bin
From here on, we assume you have the CLI installed and your environment confired properly. We also assume you either set or will replace the following environment variables:
AGAVE_USERNAME: The username you use to login to Agave for your organization.
AGAVE_PASSWORD: The password you use to login to Agave for your organization.
Configuring your enviornment
Prior to using the CLI, you will need to initialize your environment using the
tenants-init command and selecting your organization from the list. This is a one-time process that sets the proper URL base path for your tenant and stores it in a cache file on your system. You can configure the location of the authentication cache by setting the
AGAVE_CACHE_DIR environment variable. The default location is
tenants-init --tenant agave.prod
Getting your API keys
In order to communicate with Agave, you will need a set of API keys. You can use the
clients-create command to create a set.
clients-create -N "$AGAVE_USERNAME_cli_client" -D "My personal Agave cli client" -u "$AGAVE_USERNAME" -p "$AGAVE_PASSWORD" -S
-S option will save your api keys in your session cache directory,
Authentication with the API is done via OAuth2. The CLI will handle the authentication flow for you. Simply run the
auth-tokens-create command and supply your client key, secret, and username & password and a bearer token will be retrieved from the auth service and cached locally for future use. Alternatively, you can specify a bearer token at the command line by providing the
auth-tokens-create -u "$AGAVE_USERNAME" -p "$AGAVE_PASSWORD"
Accept the default values, which will hold the API keys you created in the last step. Once this returns, you will be authenticated and ready to use the Agave CLI.
If your auth token expires, the CLI will auto-refresh your credential for you. You can disable this behavior by setting the following environment variable
AGAVE_DISABLE_AUTO_REFRESH=1. You will then need to refresh your credential manually by calling
Again, accept the default values, which will hold the API keys you created in the last section and the refresh token you received when you first authenticated.
Using the CLI
The Agave CLI is broken down into the following groups of scripts
- apps* query and register apps - auth* authenticate - clients* create and manage your API keys - files* manage remote files and folders, upload, download, and transfer data - jobs* submit and manage jobs - metadata* create and manage metadata and metadata schemas - monitors* create and manage system monitors - notifications* subscribe to and manage event notifications from the platform - postits* create pre-authenticated, disposable urls - profiles* query and register users - systems* query, monitor, and manage systems - tags* create and manage resource tags - tenants* query and initialize the CLI for your tenant - transforms* convert data to/from known data formats - uuid* lookup and expand one or more Agave UUID
All commands follow a common syntax and share many of the same flags
-h for help,
-d for debug mode,
-v for verbose output,
-V for very verbose (prints curl command and full service response), and
-i for interactive mode. Additionaly, individual commands will have their own options specific to their functionality. The general syntax all commands follow is:
<command> [-hdv] <command> [-hdv] [target] <command> [-hdv] [options] [target]
Each command has built in help documentation that will be displayed when the
-h flag is specified. The help documentation will list the actions, options, and targets available for that command.
Configuring custom JSON parsers
The CLI comes bundled with two different JSON parsers. Additionally, three other parsers are supported. To specify your preferred parser, set the
AGAVE_JSON_PARSER environment variable to one of values in the following list. If no value is selected, the python parser will be used if python is available, otherwise the json-mirror API will be used.
python: The Python parser is a lightweight script written for Python 2.6+. It requires the
jsonmodule be installed (which should come standard in 2.7+). Nothing needs to be done to use this module, but you do need to have Python installed. Window users may want to consider using the
jq: jq is a command line utility written in C. It is fast, powerful, and has an extremely small memory footprint. jq has binary installers for every majory platform as well as mostly portable build. It must be installed separately.
json: The JSON Tool is a command line utility written in NodeJS. It is fast, friendly, and works out of the box. It must be installed separately and requires a Node runtime be present on the system.
native: This is the native Bash implementation from the json.sh project. It is quite a bit slower than the Python implementation and does have trouble with newline characters from time to time. That being said, it's pretty awesome for a pure Bash JSON parser.
For a 100% bash CLI with no dependencies, use the
json-mirrorparser. That will force the CLI to call out to the Agave JSON Mirror API at http://agaveapi.co/json-mirror and avoid any python dependencies.
Bash completion (beta)
The CLI come with optional bash completion support. When enabled it will complete resource ids, search fields, search operators, usernames, etc across the CLI. To enable bash completion on all CLI commands, source the included
completion/agave-cli script from your shell init script.
echo "source \"\$(dirname \$(dirname \$(which tenants-init)))/completion/agave-cli\"" >> .bashrc
You may also enabled it as needed by sourcing the file directly.
source "$(dirname $(dirname $(which tenants-init)))/completion/agave-cli"
More information on configuring bash completion behavior is provided in the