Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support grpc custom metadata pass through #730

Closed
vordimous opened this issue Jan 11, 2024 · 3 comments · Fixed by #1097
Closed

Support grpc custom metadata pass through #730

vordimous opened this issue Jan 11, 2024 · 3 comments · Fixed by #1097
Assignees
Labels
story Feature description from user's perspective

Comments

@vordimous
Copy link
Contributor

vordimous commented Jan 11, 2024

Describe the desired outcome from the user's perspective
As a gRPC service developer, I want the custom metadata added by both the client and server to be made available as it was defined for each other.

Acceptance criteria

  • Metadata included in a request from a gRPC client should be visible to the gRPC service that receives the request
  • Metadata included in a response from a gRPC service should be visible to the gRPC client that receives the response

Note: this applies to both grpc-grpc proxying and grpc-grpc-kafka-kafka-grpc-grpc proxying.

@vordimous vordimous added the story Feature description from user's perspective label Jan 11, 2024
@hedhyw
Copy link

hedhyw commented May 1, 2024

Hello, any updates on this story? Thank you!

@jfallows
Copy link
Contributor

jfallows commented May 9, 2024

@hedhyw do you still need generic metadata headers to propagate or just custom status description per #988 for now?

@hedhyw
Copy link

hedhyw commented May 9, 2024

@hedhyw do you still need generic metadata headers to propagate or just custom status description per #988 for now?

generic metadata is required too, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story Feature description from user's perspective
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants