Add support to set the value of rpc-encoding header#436
Merged
Conversation
mark200
reviewed
Feb 11, 2026
pulkit4tech
approved these changes
Mar 2, 2026
| RoutingKey string `long:"rk" description:"The routing key overrides the service name traffic group for proxies."` | ||
| RoutingDelegate string `long:"rd" description:"The routing delegate overrides the routing key traffic group for proxies."` | ||
| ShardKey string `long:"sk" description:"The shard key is a transport header that clues where to send a request within a clustered traffic group."` | ||
| RPCEncoding string `long:"rpc-encoding" description:"Override the rpc-encoding header/metadata value for gRPC and HTTP transports. This does not re-encode the request body and is intended for development."` |
Collaborator
There was a problem hiding this comment.
nit: can we add short option for this as well
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yarpc supports custom codecs defined by the user. It uses the rpc-encoding header to decide which codec to use.
This flag allows developers to overwrite the content of the rpc-encoding header so the destination service selects the desired codec.