ContainedENV
Description
This project is meant to provide utilities for writing out configuration files based on environment variables. Lots of projects seem to be implementing this on their own (Elasticsearch/Grafana), but it would be nice to have one thing that works for them all...so...here we go!
Usage
Set your environment variables with a shared prefix. Section headers should be
followed by a double underscore __
Example:
$ export MYPREFIX_foo__bar=baz
$ containedenv-config-writer.py -p MYPREFIX_
[foo]
bar = baz
Check out the help text for current usage info too:
usage: containedenv-config-writer.py [-h] -p PREFIX [-f {ini,json}]
[-o OUTPUT_FILE] [-r REFERENCE_FILE]
Convert environment variables in to a configuration file
optional arguments:
-h, --help show this help message and exit
-p PREFIX, --prefix PREFIX
Prefix of env vars to parse
-f {ini,json}, --format {ini,json}
Output file format
-o OUTPUT_FILE, --output-file OUTPUT_FILE
Outfile file path
-r REFERENCE_FILE, --reference-file REFERENCE_FILE
Load this reference file for existing/hard coded
values
Metadata
Release files for containedenv 0.0.3
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 | |
|---|---|---|---|---|
| containedenv-0.0.3.tar.gz | 3.3 kB | Without provenance | Details |
Release files / containedenv-0.0.3.tar.gz
| Download URL | containedenv-0.0.3.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
548388626a058754bc453951a7fa7f85ee68a966c6f49d9e333f8d3234503d3c
|
|
BLAKE2b-256 checksum How to use checksums |
892242e255ec53377df056ec3a65a2aabdbf85f28f4b127cbb553fc8b33e45f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.6.0 requests-toolbelt/0.8.0 tqdm/4.31.1 CPython/3.7.5
|
Security for containedenv 0.0.3
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.