Repository navigation
Expose inbound gRPC metadata w/ Rust core #12199
vprimault
started this conversation in
Temporal SDKs
Replies: 1 comment
|
Thanks for raising this - your understanding is correct: the Python SDK doesn’t currently expose custom gRPC interceptors. We are interested in better supporting access to gRPC response metadata in the SDKs based on the Rust core (though I don’t have a timeline to share today). Could you share a bit about what your custom headers contain and how you consume them in Go today? In particular, are you using them in client-side calls, worker processing, or both? In full transparency... I'm pretty new to Temporal and really appreciate learning more about your use case! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I have a use case where our self-hosted Temporal server is publishing custom gRPC headers that we would want to consume. We can do it in Go because we can add custom gRPC interceptors, but not in Python. I understand that adding gRPC interceptors in Python is not possible because of the Rust core, but would that be a possibility for example to surface gRPC metadata in input classes used by inbound interceptors, the same way we have
rpc_metadataon outbound requests?All reactions