pieman
The package contains the utilities which are used by Pieman, script for creating custom OS images for single-board computers. The utilities are:
apk_tools_version.py: fetches the latest version of the apk-tools-static package.
bsc.py: BSC (Build Status Codes) client.
bscd.py: BSC (Build Status Codes) server.
check_mutually_exclusive_params.py: checks if two specified environment variables are defined.
check_redis.py: checks if the Redis server, needed by BSC server and client, is available.
check_wpa_passphrase.py: checks if WPA passphrases are valid. A passphrase is considered as valid when 1) it’s between 8 and 63 characters and 2) it doesn’t contain any special characters. These two simple checks were borrowed from the original wpa_supplicant codebase and rewritten in Python (see wpa_supplicant/wpa_passphrase.c).
depend_on.py: sometimes one environment variable (A) can’t be specified without another one (B), so this utility helps Pieman explicitly say that A depends on B and check if B is set to true (if bool) or simply specified (in other cases) when A is set to true (if bool) or simply specified (in other cases).
du.py: provides the disk usage of the specified directory. It was developed primarily for estimating chroot environments disk usage. In some cases the utility provides more accurate result than du from GNU coreutils.
image_attrs.py: allows getting image attributes which are stored in the pieman.yml files. The utility is more high-level tool than PyYAML because it’s aware of the pieman.yml specifics.
preprocessor.py: takes a YAML file and prints it to stdout, substituting variables for their values. The preprocessor supports the ${VAR} syntax to reference variables values. There are three types of variables:
environment variables (for example, ${USER} or ${HOME});
the ${parent_node_name} builtin which contains parent nodes names, as it’s seen from the name of the variable;
every string type node.
render.py: renders config templates (which are Jinja2 templates under the hood).
wget.py: very limited GNU Wget alternative.
Installation
sudo pip3 install pieman
1 maintainer
Metadata
1 maintainer
Release files for pieman 0.19.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 | |
|---|---|---|---|---|
| pieman-0.19.0.tar.gz | 14.7 kB | Without provenance | Details |
Release files / pieman-0.19.0.tar.gz
| Download URL | pieman-0.19.0.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
643204444d4a2bb92ef8bbcb63e7c963ecbf1271422bdc6fba6f5cda9c7cb8ec
|
|
BLAKE2b-256 checksum How to use checksums |
be212b16ee434c669d457ab8051a8aac5dc0c90c5a0a7f2545420188847eae3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.8.5
|
Security for pieman 0.19.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.
