A simple Python binding for the Agave API
Branch: master
Clone or download
alejandrox1 Update changelog for v0.8.0
Signed-off-by: Jorge Alarcon Ochoa <alarcj137@gmail.com>
Latest commit 56bd208 Dec 13, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Refactoring docs structure (#71) Oct 19, 2018
agavepy Merge branch 'develop' Dec 6, 2018
docs Implement files_import (#109) Dec 5, 2018
notebooks Remove old example May 18, 2015
scripts Converging on new Actors endpoints Feb 18, 2018
testrunner Fix metadata list test in case no metadata exist and move test contai… Jan 26, 2017
tests Implement files_import (#109) Dec 5, 2018
.gitignore Issue 44 Add development container (#45) Sep 12, 2018
.travis.yml issue 48 Implement clients_create method (#52) Sep 12, 2018
AUTHORS Updating AUTHORS Feb 13, 2018
CHANGELOG.md Update changelog for v0.8.0 Dec 13, 2018
CONTRIBUTING.md Issue 44 Add development container (#45) Sep 12, 2018
Dockerfile Use root to build image Jan 6, 2016
LICENSE Align w Agave/Abaco. Add US government perpetual. Oct 11, 2017
MANIFEST.in Fixed issues publishing to PyPI, including URL and requirements. Feb 4, 2016
Makefile Implement Agave.files_list method (#82) Oct 26, 2018
PULL_REQUEST_TEMPLATE.md Refactoring docs structure (#71) Oct 19, 2018
README.rst Merge branch 'develop' Dec 6, 2018
TESTING.md issue 48 Implement clients_create method (#52) Sep 12, 2018
dev.Dockerfile issue 48 Implement clients_create method (#52) Sep 12, 2018
docker-compose.yml Mount notebooks subdirectory Nov 6, 2015
requirements-py2.txt Relaxed Jinja version to allow future versions. Set floor for configp… Jun 14, 2018
requirements.txt Issue 84 files move (#89) Nov 1, 2018
setup.cfg Add setup.cfg for wheel distribution Mar 7, 2015
setup.py Update setup.py to install the subpackage files (#80) Oct 25, 2018
tox.ini Added tox support for Py3.6 testing Feb 18, 2018



https://travis-ci.org/TACC/agavepy.svg?branch=develop https://readthedocs.org/projects/agavepy/badge/?version=latest

Python2/3 binding for TACC.Cloud Agave and Abaco APIs


Install from PyPI:

pip install agavepy

Install from GitHub checkout:

cd agavepy
python setup.py install
# or #
make install


In case you want to contribute, you should read our contributing guidelines and we have a contributor's guide that explains setting up a development environment and the contribution process.


If you already have an active installation of the TACC Cloud CLI, AgavePy will pick up on your existing credential cache, stored in $HOME/.agave/current. We illustrate this usage pattern first, as it's really straightforward.


>>> from agavepy.agave import Agave
>>> ag = Agave.restore()

Voila! You have an active, authenticated API client. AgavePy will use a cached refresh token to keep this session active as long as the code is running.

Pure Python

Authentication and authorization to the TACC Cloud APIs uses OAuth2, a widely-adopted web standard. Our implementation of Oauth2 is designed to give you the flexibility you need to script and automate use of TACC Cloud while keeping your access credentials and digital assets secure.

This is covered in great detail in our Developer Documentation but some key concepts will be highlighted here, interleaved with Python code.

The first step is to create a Python object ag which will interact with an Agave tenant.

>>> from agavepy.agave import Agave
>>> ag = Agave()
CODE                 NAME                                     URL
3dem                 3dem Tenant                              https://api.3dem.org/
agave.prod           Agave Public Tenant                      https://public.agaveapi.co/
araport.org          Araport                                  https://api.araport.org/
designsafe           DesignSafe                               https://agave.designsafe-ci.org/
iplantc.org          CyVerse Science APIs                     https://agave.iplantc.org/
irec                 iReceptor                                https://irec.tenants.prod.tacc.cloud/
sd2e                 SD2E Tenant                              https://api.sd2e.org/
sgci                 Science Gateways Community Institute     https://sgci.tacc.cloud/
tacc.prod            TACC                                     https://api.tacc.utexas.edu/
vdjserver.org        VDJ Server                               https://vdj-agave-api.tacc.utexas.edu/

Please specify the ID of a tenant to interact with: araport.org
>>> ag.api_server

If you already now what tenant you want to work with, you can instantiate Agave as follows:

>>> from agavepy.agave import Agave
>>> ag = Agave(api_server="https://api.tacc.cloud")


>>> from agavepy.agave import Agave
>>> ag = Agave(tenant_id="tacc.prod")

Once the object is instantiated, interact with it according to the API documentation and your specific usage needs.

Create a new Oauth client

In order to interact with Agave, you'll need to first create an Oauth client so that later on you can create access tokens to do work.

To create a client you can do the following:

>>> from agavepy.agave import Agave
>>> ag = Agave(api_server='https://api.tacc.cloud')
>>> ag.clients_create("client-name", "some description")
API username: your-username
API password:
>>> ag.api_key
>>> ag.api_secret

You will use the api key and secret to generate Oauth tokens, which are temporary credentials that you can use in place of putting your real credentials into code that is interacting with TACC APIs.

Reuse an existing Oauth client

Once you generate a client, you can re-use its key and secret. Clients can be created using the Python-based approach illustrated above, via the TACC Cloud CLI clients-create command, or by a direct, correctly-structured POST to the clients web service. No matter how you've created a client, setting AgavePy up to use it works the same way:

>>> from agavepy.agave import Agave
>>> ag = Agave(api_server='https://api.tacc.cloud',
...            username='mwvaughn',
...            client_name='my_client',
...            api_key='kV4XLPhVBAv9RTf7a2QyBHhQAXca',
...            api_secret='5EbjEOcyzzIsAAE3vBS7nspVqHQa')

The Agave object ag is now configured to talk to all TACC Cloud services.

Generate an Access Token

In order to interact with the TACC cloud services in a more secure and controlled manner - without constantly using your username and password - we will use the oauth client, created in the previous step, to generate access tokens.

The generated tokens will by defualt have a lifetime of 4 hours, or 14400 seconds.

To create a token

>>> ag.get_access_token()
API password:
>>> ag.token

Keep in mind that you will need to create an oauth client first!

Saving your credentials

To save your process (api key, api secret, access token, refresh token, tenant information) you can use the method Agave.save_configs()

>>> ag.save_configs()

By default, Agave.save_configs will store credentials in ~/.agave. It will save all session in ~/.agave/config.json and, for backwards-compatibility with other agave tooling, it will save the current session in ~/.agave/current.

The refresh token

Nobody likes to change their password, but they have to if it leaks out into the wild. A tragically easy way for that to happen is in committed code or a Docker container where it's been hard-coded. To get around this, AgavePy works with the TACC authentication APIs to support using a refresh token. Basically, as long as you have the apikey, apisecret, and the last refresh token for an authenticated session, you can renew the session without sending a password. Neat, right? Let's build on the ag object from above to learn about this.

Let's start by inspecting its token property, which will also demonstrate how you can access token data programmatically for your own purposes.

>>> ag.token.token_info
{u'access_token': u'14f0bbd0b334e594e676661bf9ccc136', 'created_at':
 1518136421, u'expires_in': 13283, 'expires_at': 'Thu Feb  8 22:15:04',
 u'token_type': u'bearer', 'expiration': 1518149704, u'scope': u'default',
 u'refresh_token': u'b138c49040a6f67f80d49a1c112e44b'}
>>> ag.token.token_info['refresh_token']