Pigeon Config
Pigeon Config is a tool for managing a set of YAML configuration files. It is based on Adobe's himl, and compiles a collection of YAML files, merging keys as necessary. It outputs a separate YAML file for each top level key. It can also check if the compiled YAML files need to be updated.
Command Line Usage
usage: pigeon-config [-h] [-c] [-r ROOT] [-o OUTPUT] [leaf]
positional arguments:
leaf The leaf directory to use.
options:
-h, --help show this help message and exit
-c, --check Check if pigeon-config should be run again.
-r ROOT, --root ROOT The path to use as the current working directory.
-o OUTPUT, --output OUTPUT
The directory to output the configuration files to.
Pigeon Config has two modes, 1. to compile the configuration (the default), and 2. to check if the configuration needs to be recompiled.
Compiling
When compiling a configuration, Pigeon Config will find all YAML files in the directory tree starting from the specified leaf directory, and stopping one level short of the current directory, or the root directory if specified. The compiled output is then saved to a directory named materialized relative to the current directory, or to the output directory if specified.
Checking
To check if a configuration should be recompiled, Pigeon Config can be run with the --check option. In this case, Pigeon Config checks if any files in the current directory, or root directory if specified, are newer than the files in the output directory, again defaulting to materialized. In this mode, Pigeon Config will output the files that are newer than the output, and exits with a nonzero exit code when such files exist. Note: the way the root directory option is treated is different in the configuration checking mode, than in the compiling mode.
Removing Keys
To remove keys from the compiled configuration, they may be set to null. This removal is performed at all levels.
Installing
Pigeon Config can be installed from the Python Package Index using pip install pigeon-config.
Docker
A Dockerfile is also provided so Pigeon Config can be run inside a Docker container, and included as part of a Docker compose file.
Metadata
Release files for pigeon-config 0.2.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 | |
|---|---|---|---|---|
| pigeon_config-0.2.3.tar.gz | 30.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pigeon_config-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 79.4 kB
Release files / pigeon_config-0.2.3.tar.gz
| Download URL | pigeon_config-0.2.3.tar.gz |
|---|---|
| Size | 30.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a06974d2bec38487011622be7acc80fe2d2a6ea0aca61edc72ffb41d8772d4e
|
|
BLAKE2b-256 checksum How to use checksums |
731efd10e63f0a433067368dc173fd43dc46ac0ef06099c0fd8bf53bd059ede0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 24, 2025.
Transparency logRelease files / pigeon_config-0.2.3-py3-none-any.whl
| Download URL | pigeon_config-0.2.3-py3-none-any.whl |
|---|---|
| Size | 48.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8fa2bcb645f81757ab2ccc7192e15b3db53288d52c5ad0f83db75b06325f2960
|
|
BLAKE2b-256 checksum How to use checksums |
b4d834bf15d9514c05493ce0057087836cdeb502c775a39fde7cc06936e62c9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 24, 2025.
Transparency logSecurity for pigeon-config 0.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pigeon_config-0.2.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 24, 2025.
Transparency logA 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.