Inngest Python SDK: Encryption
This package provides encryption for the Inngest Python SDK.
Usage
Setting encryption middleware on the client will turn on encryption for events and steps in all functions:
import inngest
from inngest_encryption import EncryptionMiddleware
inngest.Inngest(
name="my-app",
encryption_key="my-encryption-key",
middleware=[EncryptionMiddleware.factory("my-secret-key")],
)
When sending events or invoking functions, only the encrypted field will be encrypted:
await step.send_event(
"my-step",
inngest.Event(
data={
# Everything in this field will be encrypted.
"encrypted": {
"phone": "867-5309",
},
# Not encrypted.
"user_id": "abc123",
},
name="my-event",
),
)
await step.invoke(
"invoke",
function=child_fn_async,
data={
# Everything in this field will be encrypted.
"encrypted": {
"phone": "867-5309",
},
# Not encrypted.
"user_id": "abc123",
},
)
The entire step.run output is encrypted:
def _my_step() -> dict[str, object]:
# Encrypted when sending back to the Inngest server.
return {"msg": "hello"}
output = await step.run("my-step", _my_step)
# Decrypted within this function.
print(output)
Key rotation
When rotating the encryption key, you may still have active functions runs whose data is encrypted with the old key. To decrypt these, you can use the fallback_decryption_keys option:
inngest.Inngest(
name="my-app",
encryption_key="my-encryption-key",
middleware=[
EncryptionMiddleware.factory(
"new-secret-key",
fallback_decryption_keys=["old-secret-key"],
),
],
)
If decryption fails with the new key, the encryption middleware will fall back to the old key.
Metadata
Release files for inngest-encryption 0.1.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 | |
|---|---|---|---|---|
| inngest_encryption-0.1.0.tar.gz | 5.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inngest_encryption-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.3 kB
Release files / inngest_encryption-0.1.0.tar.gz
| Download URL | inngest_encryption-0.1.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70bfe640a7f7e479c955dd34269e3f9c3154fa83c0a9d68b44563b2db1cf4300
|
|
BLAKE2b-256 checksum How to use checksums |
09e947ac0f9960989485baafeb0a32a0796c25340a29106cb3d6f34919734048
|
| 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 Mar 11, 2025.
Transparency logRelease files / inngest_encryption-0.1.0-py3-none-any.whl
| Download URL | inngest_encryption-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddb8efdc602e14dc606415b2b1d333099ec0afd4efade7ec4ed971bc88c26bf9
|
|
BLAKE2b-256 checksum How to use checksums |
d372f00f3d1f59ac994eec1a8aa7861843dc2dbd0d0fe6359c7792f68b2223c7
|
| 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 Mar 11, 2025.
Transparency logSecurity for inngest-encryption 0.1.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 inngest_encryption-0.1.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 Mar 11, 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.