Google Env
A simple utility which pulls development-time values from a Google spreadsheet. This allows you to share dev secrets in a semi-secure way.
Usage
-
You need an Oauth credentials JSON file. One person needs to register an Oauth app in the Google Console and then download the credentials JSON file. Place this file in
$HOME/google_env_creds.json. -
Now create a
.envfile in your code project. Reference the spreadsheet which contains your secrets at the top of the file:
.env:
# GOOGLE_ENV: https://docs.google.com/spreadsheets/d/17fcDBp5tez9JFtRwucDW5-wq3jgmzq8s-oWcnUljyR0!Sheet1
Note that the sheet name should be after the '!' at the end.
-
Install the
google_envpackage:pip install google_env -
Now run the
google_envscript directory containing your .env file$ google_env
The first time you run it you will be sent through the Google Oauth flow in the browser.
Your access key to the spreadsheet will then be cached in a local file in
~/.google_env_token.
Now the contents of your spreadsheet are downloaded and inserted into the .env
file. Your spreadsheet should have 2 columns, the key and the value, with no header.
So if your sheet looks like this:
| A | B | |
|---|---|---|
| 1 | key1 | mysecretkey1 |
| 2 | AWS_ACCESS | foobar |
Then the resulting .env file will be rewritten as:
# GOOGLE_ENV: https://docs.google.com/spreadsheets/d/17fcDBp5tez9JFtRwucDW5-wq3jgmzq8s-oWcnUljyR0
key1=mysecretkey1
AWS_ACCESS=foobar
# END_GOOGLE_ENV
Note that you should leave the closing comment line. This will allow you to
re-run google_env any time to update keys from the spreadsheet.
If you need to override any values, simply add a second assignment for that
key lower down in your .env file.
Doing other things with Google Sheets
This package can be used to easily retrieve information from any Google Sheet.
> import google_env
> for row in google_env.read_sheet(sheet_id, sheet_range):
# row will be an array of column values for each row in the sheet
print(row)
Where sheet_id is like 1mhs7mW7dBK_lhNYB4hZFwdF1QXWSEzl6ITsY50DGx9M and
sheet_range is a Sheets range like <name>!<range spec> like
Sheet1!A1:G20.
Metadata
Release files for google-env 0.4.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 |
|---|---|---|---|---|
| google_env-0.4.0.tar.gz | 5.4 kB | Without provenance | Details for google_env-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| google_env-0.4.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for google_env-0.4.0-py2.py3-none-any.whl |
Total release size: 10.1 kB
Release files / google_env-0.4.0.tar.gz
| Download URL | google_env-0.4.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0286b249866745ebbfccef80d6afbccc05869670b44e85488400dd922f1564a
|
|
BLAKE2b-256 checksum How to use checksums |
3b7e16d4cb6b2ce7b3f4f2ad06b8267555abef1f84f11bedbc6e5b1b0219f2f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.33.0 CPython/2.7.16
|
Release files / google_env-0.4.0-py2.py3-none-any.whl
| Download URL | google_env-0.4.0-py2.py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c3dbc379d2bb0d3039a81cd2b4702d28d698201dedbce7998ccb97139d52553a
|
|
BLAKE2b-256 checksum How to use checksums |
3fa98de81115bb3bc9c21c0ba35edf80987fd3ea3d2bb50a746ac66e23a082af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.33.0 CPython/2.7.16
|
Security for google-env 0.4.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.