This release is a pre-release and may not be stable for production use.
Overview
This package provides a simple wrapper around Google APIs such as Cloud Compute, IAM, Deployment Manager, and other cloud-related APIs.
It is used internally by Infolinks for provisioning and deployments, and has proven useful, so we’ve decided to share it! Note that this is still work in progress - our internal version is currently more comprehensive in its coverage of Google’s APIs than this version; we will slowly transition more & more APIs from our internal version to this open version, so stay tuned!
NOTE: Google APIs wrapper requires Python 3.5 and above.
Installation
Installing this package from PyPy is simple, using pip:
pip install google-api-wrapper
You can add the --upgrade or -U flag to upgrade it if you already have it installed.
APIs
The package’s entry point to the APIs is the Cloud module. This module contains a single class - the Cloud class, which you create an instance of using a Google Cloud JSON credentials file (usually generated from a service account) and one or more scopes (scopes are essentially the list of permissions you are requesting to use). By default, if you do not provide any scopes, the framework will ask for the https://www.googleapis.com/auth/cloud-platform scope which means full permissions. Narrow it down to request more specific permissions instead.
Once you have an instance of the Cloud class, it can provide you with more specific Google Cloud API wrappers:
Compute: this API contains Google Compute APIs such as creating disks & instances, modifying instance group members, etc.
IAM: this API is used for managing user and service accounts. Not implemented yet.
Deployment Manager: this API is used for managing deployments using the Google Deployment manager service. Not implemented yet.
More to come (Network, Pub/Sub, etc)
Building
Google APIs wrapper requires Python 3.5 and above. This is a hard requirement unfortunately. That aside, however, building it is fairly simple - you just use pyvenv and pip install -e.
We recommend reading Packaging Guide and the Virtual Environments Guide, but we’ve compiled a simple & quick how-to for your convenience:
Clone the repository:
git clone git@bitbucket.org:infolinks/google-api-wrapper.git
Set up a virtual environment:
pyvenv <virtual-env-directory>
Activate the virtual environment (once for every shell/terminal you will be using to build or develop in it):
source <virtual-env-directory>/bin/activate
Install required libraries:
pip install wheel google-api-python-client twine
Install the cloned copy of the source code using:
pip install -e <git-checkout-of-google-api-wrapper>
You can now modify the source code freely.
When you want to test it, simple run your Python program which will import the googleapiwrapper package inside it.
Releasing
To release a new version, first please ensure you are able to successfully build using the above section’s instructions (including registration to PyPi and PyPi testing.)
There are two methods to releasing:
The deploy.sh script (recommended)
Manual release
Both methods achieve the same thing, but the 1st one is by far the easiest.
Automated releasing
The project comes with a built-in bash script (sorry Windows users!) which performs everything the manual method does. To use, simply invoke the script, like this:
./deploy.sh <version>
The version should be a valid Python version - usually something like 1.0.0b3.
Manual release
To perform a manual release, or if the deploy.sh script failed and left you in an inconsistent state, do the following:
Update the version in setup.py
Commit & push the changes to Git:
git add setup.py git commit -m "preparing version X.Y.Z" git push git tag -a "X.Y.Z" -m "Version X.Y.Z" git push origin "X.Y.Z"
Build the package:
rm -rf build dist python setup.py sdist bdist_wheel
Now that we’ve created the distributions, we need to ensure we are able to upload our package to PyPi. To do this, ensure you have an account over at PyPi as well as at PyPi Testing. We will be using Twine to perform the upload.
Ensure you’ve created the ~/.pypirc file, which should look like this (don’t forget to fill-in your credentials inside it!):
[distutils] index-servers= pypi pypitest [pypitest] repository = https://testpypi.python.org/pypi username = <username> password = <password> [pypi] repository = https://pypi.python.org/pypi username = <username> password = <password>Note that your own file might contain additional repositories - that’s ok. You will only be using pypitest and pypi when working with this project though.
The project needs to be registered with PyPi (to reserve the package name). Note that this only needs to be done once in the project’s lifetime, and has already been done for you! You DO NOT need to run this. But for documentational purposes, here is the command to do it:
twine register --repository pypitest dist/google_api_wrapper-<version>-py3-none-any.whl twine register --repository pypi dist/google_api_wrapper-<version>-py3-none-any.whl
Now we can upload the package. We recommend first uploading it to the PyPi Testing package index in order to verify it’s working properly. Here’s how:
twine upload --repository pypitest dist/*
Once you’re satisified with the results, you can upload it to the public repository, like this:
twine upload --repository pypi dist/*
Restore the version in setup.py to a dev version (eg. 1.1.0dev)
Release files for google-api-wrapper 2.0.0a1
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 |
|---|---|---|---|---|
| google-api-wrapper-2.0.0a1.tar.gz | 8.1 kB | Without provenance | Details for google-api-wrapper-2.0.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| google_api_wrapper-2.0.0a1-py3-none-any.whl | Python 3 | none | any | Details for google_api_wrapper-2.0.0a1-py3-none-any.whl |
Total release size: 20.6 kB
Release files / google-api-wrapper-2.0.0a1.tar.gz
| Download URL | google-api-wrapper-2.0.0a1.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d8e92cce2d648c79b1ee5adb7d47284185a853a744aa0809225cc2e947f8f75
|
|
BLAKE2b-256 checksum How to use checksums |
0a6a76725fa6b59d79a986da08d44237b66f4d53472411f7cc757b2b3bfc8e50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / google_api_wrapper-2.0.0a1-py3-none-any.whl
| Download URL | google_api_wrapper-2.0.0a1-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
57d25ea9e564e1787abd927ff31f51191cbc0b872839f14f99dafbe67adaef65
|
|
BLAKE2b-256 checksum How to use checksums |
6b915b843d0615aa497503ef53be6ae0428fdc6a2bf01eb65877807fdd3c9113
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for google-api-wrapper 2.0.0a1
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.
