You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
grpcurl -v -d '{"queries":[{"cql":"UPDATE bookmarking.bookmarks USING TTL :ttl AND TIMESTAMP :timestamp SET streamPosition = :streamposition, created = :created WHERE pvid = :pvid AND providerterritory = :providerterritory AND provider = :provider AND householdId = :householdid AND timeBucket = :timebucket and personaId = :personaid;"}]}' -proto query.proto -proto stargate.proto -plaintext localhost:4312 stargate.Stargate/ExecuteBatch
I'm unsure if this is a bug or if this isn't documented or supported.
Take HTTP: Camouflage mocks HTTP by having you provide the entire HTTP response in your *.mock file, including status code headers, etc. This would allow me to test scenarios like when the server responds with a HTTP 400, then I can verify my app behaves accordingly.
Similarly in gRPC we have status codes and I may want to do the same thing where I configure camouflage to return GRPC 16 "Unauthorized" so that I can verify my app behaves accordingly when such a thing happens. I don't see it documented.
Since I'm proxying with envoy to camouflage, I also would like to set headers but I know I may be asking for too much there.
Describe the bug
Hi, apologies in advance if the answer to my question is trivial but I don't have any experience with gRpc and protobufs.
What I would like to achieve is:
To Reproduce
Steps to reproduce the behavior:
mocks:
protos:
Response:
Expected behavior
It's should be possible to define request matchers and return responses accordingly.
Thanks,
Barnabas
The text was updated successfully, but these errors were encountered: