sabu-chassis
sabu-chassis is a shared Sabu library that provides reusable utilities for multiple services.
It is designed for cross-cutting concerns that should be imported directly by services (for example: logging setup and shared runtime conventions), instead of being exposed as a standalone service.
Why this package exists
In Sabu, some capabilities are best delivered as code dependencies rather than API calls.
Using sabu-chassis as a dependency makes it easier to:
- Reuse the same behavior across services.
- Keep service internals consistent.
- Ship functionality (not inter-service data exchange) in a versioned Python package.
Current scope
At the moment, the primary implemented utility is logging configuration.
The logging setup is currently tuned for one service context. As the microservices chassis effort progresses, this will be normalized so all Sabu services can use a common logging standard in later versions.
Installation
Dockerizing and using in services independently
pip install sabu-chassis
Installing as a dependency (e.g., inside Dockerized services)
cd libs/sabu_chassis
pip install .
Developing locally (cloning the repository)
from sabu_chassis.logging import configure_logging, get_logger, set_request_id
configure_logging()
set_request_id('req-123')
logger = get_logger(__name__)
logger.info('service_started')
Libraries should use get_logger(__name__) and leave configure_logging() to
the application or workflow entry point.
Optional environment variables commonly used by the logging module include:
LOG_LEVELWERKZEUG_LEVELLOG_SERVICELOG_ENVLOG_DIR_BASE
Sabu
Sabu is a sector-based carbon-emission evaluation framework built with a microservices architecture.
Each module runs as an independent service. Current services focus on building life-cycle assessment and city-scale geospatial cleaning/validation workflows. Alongside services, Sabu also includes shared Python libraries such as sabu-chassis to provide reusable internal functionality.
Roadmap note
sabu-chassis will continue to grow as a shared library for Sabu services, with future versions expanding beyond logging into additional standardized service utilities.
Metadata
Release files for sabu-chassis 0.1.1
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 |
|---|---|---|---|---|
| sabu_chassis-0.1.1.tar.gz | 16.6 kB | Without provenance | Details for sabu_chassis-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sabu_chassis-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for sabu_chassis-0.1.1-py3-none-any.whl |
Total release size: 32.3 kB
Release files / sabu_chassis-0.1.1.tar.gz
| Download URL | sabu_chassis-0.1.1.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
087b4ae75e83a056f0d1967c49aa205f915f63e1b4adacf43bf7ebbdf25c1ed7
|
|
BLAKE2b-256 checksum How to use checksums |
71e585910ab1e1fbebde57efc2116c5a852a10333de442f01329150f44534c3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.19
|
Release files / sabu_chassis-0.1.1-py3-none-any.whl
| Download URL | sabu_chassis-0.1.1-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3dd73dd42381313cf6209e09a4d32df6a4028aa66d68e1662372f8fe5590a5d4
|
|
BLAKE2b-256 checksum How to use checksums |
ad58366a47199ed6ecc9a6b193b9e5a83f50c0540772c02d5af68b4495237812
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.19
|
Security for sabu-chassis 0.1.1
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.