huy
11/19/2022, 1:48 AM/graphql
. the request is done through 2 methods:
1. lambda sdk call by another back end service
2. front end POST through the aws api gateway
in both cases, the endpoints are not set up in the application itself but rather through lambda or aws api gateway (and the cdk)
when running the test on the provider side, i always get 404 because the endpoint /graphql
doesn't exist when the test is running locally.
any ideas how to get around this?
is using a Message Contract rather than an HTTP contract the best use here?huy
11/19/2022, 1:53 AMuglyog
huy
11/21/2022, 4:01 PM/graphql
and bypass the gateway layerMatt (pactflow.io / pact-js / pact-go)
huy
11/22/2022, 6:18 PM/graphql
endpoint in a front end. the /graphql
endpoint is set up in AWS CDK and api gateway. our provider microservices are not aware of the endpoints when testing locally.
i used WireMock to listen for the /graphql
post and pass it along to the logic controllerMatt (pactflow.io / pact-js / pact-go)