Add support for XSVM grpc server reflection #4010
Merged
Conversation
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
Signed-off-by: Joshua Kim <20001595+joshua-kim@users.noreply.github.com>
mpignatelli12
approved these changes
Jun 12, 2025
meaghanfitzgerald
approved these changes
Jun 12, 2025
StephenButtolph
approved these changes
Jun 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why this should be merged
Allows clients to discover the service definition + request/response types without knowing the proto file
How this works
Registers the xsvm grpc server into the grpc reflection api. Clients who don't know the proto file (postman, grpcurl) can query the reflection api to discover the available grpc services + its types to be able to communicate with the server without having the proto definition.
How this was tested
Tested manually
Need to be documented in RELEASES.md?
No