dirigent-blocks
The built-in pack: one install that brings every block family dirigent ships -- base, http, storage, execute, sql, jq and queues -- and the outbound alert channels beside them.
The three channels here are webhook, slack and email, each with a connection kind of the
same id, so an alert is delivered through the one connection path every credential in this
instance goes through. The fourth channel, log, is dirigent-block-base's, because it needs
no credential.
A family is installable on its own: a worker that only runs jq needs
dirigent-block-jq and nothing else. This package is what an instance installs to have the lot.
1 maintainer
Release files for dirigent-blocks 0.18.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dirigent_blocks-0.18.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / dirigent_blocks-0.18.0-py3-none-any.whl
| Download URL | dirigent_blocks-0.18.0-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b24196d608fc7ae166c7f5af185e5c23d5739458a61213b41162bf3ee53fc5e8
|
|
BLAKE2b-256 checksum How to use checksums |
ce8598bd263012e96b619f120318e4ace684cbc345f2e123afb9bd3bd50044cf
|
| 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 21, 2026.
Transparency log
