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.

Sign up for GitHub

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

Jump to bottom

How strict should grpc-replay be when matching requests/responses? #1

Open

bradleyjkemp opened this issue Apr 30, 2019 · 0 comments

Labels

design question grpc-replay

Owner

bradleyjkemp commented Apr 30, 2019

Things that could be matched on:

Do request/response messages need to be an exact (byte-level) match of those in the dump?
Is it possible to ignore mismatches in certain fields?
How are "Status-like" RPCs handled (where you poll with some sort of ID and the response changes over time from e.g. starting -> running -> complete)
- Is it ok to ignore the exact number of duplicate messages as long as the transitions match?

bradleyjkemp added the design question label

bradleyjkemp mentioned this issue

How smart can grpc-replay be when inferring dynamic/ID fields? #2

Open

bradleyjkemp added the grpc-replay label

bradleyjkemp mentioned this issue

grpc-fixture should match based on destination/authority #39

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment