apikey
Installation
The apikey git repo is available as PyPi package
pip install "apikey>=0.2.1" pip install git+ssh://git@github.com/ulf1/apikey.git
Usage
Store in default location $HOME/.apikey-store
import apikey
apikey.save("service1", "supersecret")
apikey.save("service2", "donttellanyone")
apikey.save("service3", "aboutthiskey")
key1 = apikey.load("service1")
key2 = apikey.load("service2")
key3 = apikey.load("service3")
Store in a specific file
apikey.save("service42", "topsecretkey", filename="/srv/.secretkeys")
key = apikey.load("service42", filename="/srv/.secretkeys")
Appendix
Install a virtual environment
python3.6 -m venv .venv
source .venv/bin/activate
pip install --upgrade pip
pip install -r requirements-dev.txt
Python commands
Check syntax: flake8 --ignore=F401 --exclude=$(grep -v '^#' .gitignore | xargs | sed -e 's/ /,/g')
Run Unit Tests: pytest
Publish
pandoc README.md --from markdown --to rst -s -o README.rst
python setup.py sdist
twine upload -r pypi dist/*
Metadata
Release files for apikey 0.2.4
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 |
|---|---|---|---|---|
| apikey-0.2.4.tar.gz | 6.6 kB | Without provenance | Details for apikey-0.2.4.tar.gz |
Release files / apikey-0.2.4.tar.gz
| Download URL | apikey-0.2.4.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4efe5f906110242cac7cf7f0e92cc414922236f81a64dcb55a58ea7ecce2577
|
|
BLAKE2b-256 checksum How to use checksums |
e883b5cb02a965ae278465bf9f9d6388b45203be4392a0b5c15fe346f95cc243
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/56.0.0 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.9
|
Security for apikey 0.2.4
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.