Invoke step by id - Encryption middleware

[dvuletas]

Hello @amh4r and others,

I need your help with one thing.
We are using encryption middleware during publishing events for Inngest.

Since step invoke_by_id is used in our case (we are chaining functions), we saw that all data are encrypted by default. Is it possible to tell which field to not encrypt or maybe to force encryption for only the block that we think is sensitive?

Root function: [ENCRYPTED only sensitive block of data]

• Function 1 (invoke by id) [ENCRYPTED whole body]
• Function 2 (invoke by id) [ENCRYPTED whole body]

Inngest SDK version: 0.4.17
Python version: 3.13

[amh4r]

That currently isn't possible with inngest.experimental.encryption_middleware, but we'll likely add it in the future! We're still gathering more use cases before making big changes.

In the meantime, you could copy inngest.experimental.encryption_middleware into your codebase and modify it to suit your needs.

Here's where it encrypts invoke data:
https://github.com/inngest/inngest-py/blob/main/inngest/experimental/encryption_middleware.py#L282

You could maybe add a new invoke_encryption_field constructor arg and do something similar to this:
https://github.com/inngest/inngest-py/blob/main/inngest/experimental/encryption_middleware.py#L235-L240