eai-configgy
Opinionated YAML + environment configuration loader for Extensibility AI services.
Load a committed config.yaml with EnvYAML interpolation, then select the block for CONFIG_ENV (default, staging, or prod).
Install
uv add eai-configgy
Or with pip:
pip install eai-configgy
Usage
from eai_configgy import Config, ConfigEnv
cfg = Config(section="myapp", env=ConfigEnv.DEFAULT)
Development
Use uv for dependency management:
uv sync --extra dev
uv run pytest
Publish
Tagged releases (v*) publish to public PyPI via .github/workflows/publish-pypi.yml (Trusted Publishing, GitHub Environment pypi) and also to Artifact Registry via .github/workflows/deploy.yml for internal indexes.
Repository: ExtensibilityAI/eai-configgy
First public release (maintainers)
Do these after this repo’s rename PR is on main, before tagging v0.3.0. A pending publisher does not reserve the name until the first successful upload.
-
Rename the GitHub repo to
eai-configgy(Settings → General → Repository name). Keep GitHub’s redirect. Locally:git remote set-url origin git@github.com:ExtensibilityAI/eai-configgy.git. -
Create GitHub Environment
pypi: required reviewers; deployment branches/tags restricted tov*. No secrets (OIDC). Optional: Environmenttestpypifor dry-runs. -
PyPI account: register at https://pypi.org (2FA required). Prefer a PyPI organization (e.g.
extensibility-ai) so the project is not personal-owned. Confirm https://pypi.org/project/eai-configgy/ is unused (404). -
Pending Trusted Publisher (PyPI Account → Publishing, not a project page):
Field Value PyPI project name eai-configgyOwner ExtensibilityAIRepository eai-configgyWorkflow name publish-pypi.ymlEnvironment pypi -
GAR WIF after the GitHub rename: set
github.repo: ExtensibilityAI/eai-configgyininfrastructure-core-gcp/pulumi/python_package/configgy/Pulumi.{staging,prod}.yaml, thenpulumi upthose stacks (only with explicit approval). -
Tag and approve:
git tag v0.3.0 && git push origin v0.3.0. Approve thepypienvironment. Confirm https://pypi.org/project/eai-configgy/0.3.0/. -
Optional: make the GitHub repository public after LICENSE and SECURITY.md are on
main.
1 maintainer
Metadata
1 maintainer
Release files for eai-configgy 0.3.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 |
|---|---|---|---|---|
| eai_configgy-0.3.0.tar.gz | 7.7 kB | With provenance | Details for eai_configgy-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eai_configgy-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for eai_configgy-0.3.0-py3-none-any.whl |
Total release size: 14.9 kB
Release files / eai_configgy-0.3.0.tar.gz
| Download URL | eai_configgy-0.3.0.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a8c686af701849a95879c6c083f3b843fea8ebc0d539034481aced1126f26eb
|
|
BLAKE2b-256 checksum How to use checksums |
2f3f9c66eb4232f08714b78a6ecc65a9809d1ec709eee0d217d8ccb3d0ab7938
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 4, 2026.
Transparency logRelease files / eai_configgy-0.3.0-py3-none-any.whl
| Download URL | eai_configgy-0.3.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec9943b7cf5794062d7a0636f0c9801c2c9401599dbeb209518aa71f4747af0f
|
|
BLAKE2b-256 checksum How to use checksums |
f4c5a8b88883bf862666891d13ea771ded82680a4cfb2d904ab431de63a3416b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 4, 2026.
Transparency logSecurity for eai-configgy 0.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for eai_configgy-0.3.0.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 Sep 4, 2026.
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.
