GRPC Passthrough documentation and test server update #10676
Merged
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.
Description
Update Auth passthrough docs:
Update the GRPC/HTTP passthrough example servers to log the full requests received if the
REQUEST_LOGGING
env var is set and update to current version of go/dependenciesUpdate GRPC passthrough documentation to describe use of
settings.extauth.requestBody
Code changes
Update the GRPC/HTTP passthrough example servers to log the full requests received if the
REQUEST_LOGGING
env var is setAPI Changes
Update GRPC passthrough documentation to describe use of
settings.extauth.requestBody
Docs changes
GRPC/HTTP passthrough examples updaetd
Context
Users asked for GRPC body passthrough, and an RFE was passed through the engineering team, but the functionality already existed. This functionality relies on
settings.extauth.requestBody
being set, and that was not documented in appropriate place.Testing steps
validated by running through both HTTP and GRPC passthrough examples in the same cluster
Checklist: