datasette-unsafe-expose-env
Datasette plugin to expose some environment variables at /-/env - for debugging
⚠️ This plugin is no longer maintained. datasette-expose-env is recommended as a safe replacement that only exposes environment variables that you have explicitly configured.
Installation
Install this plugin in the same environment as Datasette.
$ datasette install datasette-unsafe-expose-env
Usage
Once installed, the plugin will show a list of environment variables at /-/env
It will redact the following variables by default:
DATABASE_URLGPG_KEYDATASETTE_SECRET
You can configure an alternative set of redacted secrets in your metadata.yml configuration:
plugins:
datasette-unsafe-expose-env:
redact:
- DATASETTE_SECRET
- GPG_KEY
- MY_OTHER_SECRET
Once again though: only use this plugin if you need it for debugging purposes and are absolutely certain it won't expose any valuable information. If in doubt, do not use this at all.
Development
To set up this plugin locally, first checkout the code. Then create a new virtual environment:
cd datasette-unsafe-expose-env
python3 -mvenv venv
source venv/bin/activate
Now install the dependencies and test dependencies:
pip install -e '.[test]'
To run the tests:
pytest
Metadata
Release files for datasette-unsafe-expose-env 0.1.1
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 |
|---|---|---|---|---|
| datasette-unsafe-expose-env-0.1.1.tar.gz | 2.6 kB | Without provenance | Details for datasette-unsafe-expose-env-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datasette_unsafe_expose_env-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for datasette_unsafe_expose_env-0.1.1-py3-none-any.whl |
Total release size: 5.6 kB
Release files / datasette-unsafe-expose-env-0.1.1.tar.gz
| Download URL | datasette-unsafe-expose-env-0.1.1.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32a90e47c65b1536887e631ea07ebbccba363ddd21bbc841ecd284039c65c488
|
|
BLAKE2b-256 checksum How to use checksums |
23fccc5342b6ab32be4c1b2d005535b465437d8f22c7ae07ce0eb671a585c8e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Release files / datasette_unsafe_expose_env-0.1.1-py3-none-any.whl
| Download URL | datasette_unsafe_expose_env-0.1.1-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
853a9c44414f731e012fbdd0da3a3616e7c7f620c9f866e18940725a71b70b65
|
|
BLAKE2b-256 checksum How to use checksums |
b19ebc54e379b8aaf5e1b6732e83fe0e1c1377610e4efd4fce433ce8f71725ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Security for datasette-unsafe-expose-env 0.1.1
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.