env2fs: write env vars to filesystem (CI tool)
Write a file with an env var content or a set of env vars.
Usage example:
env2fs ~/.ssh/id_rsa SSH_KEY fmod=600 dmod=700
Note that the missing dollar sign is intendent to prevent evaluation from the parent shell itself.
The above example writes the contents of the $SSH_KEY environment variable into ~/.ssh/id_rsa, with a mode of 600 and 700 for any parent directory that will be automatically created if necessary.
To write an env file, pass a variable name that ends with underscore, ie:
export staging_pgpass=foo env2fs staging.env staging_
Will write staging.env with contents:
pgpass=foo
Extra CLI options:
--dryrun Do not actually touch the fs --verbose,-v Verbose output
Release files for env2fs 0.2.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 |
|---|---|---|---|---|
| env2fs-0.2.0.tar.gz | 2.3 kB | Without provenance | Details for env2fs-0.2.0.tar.gz |
Release files / env2fs-0.2.0.tar.gz
| Download URL | env2fs-0.2.0.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3498b76c09567ab9df9d27a3c05a2e7e98a952f8f4e0a5ff7aba3a273d46e59
|
|
BLAKE2b-256 checksum How to use checksums |
306176724af631e78a3a73450b0726752ca7880c841f7e9ecf1ea45e69a1d35b
|
| 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/39.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.6
|
Security for env2fs 0.2.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.
