Using different requests context

[shevchenkonik]

I have a lot of 3rd party REST services and all of them have different required request contexts (headers & body), do we have an easy way to set up it within GraphQL Mesh?

[ardatan]

Individual sources are already configured seperately in GraphQL Mesh. If you give more specific examples, I can help better.

[shevchenkonik]

Of course, thank you!

Let's imagine that I would like to use GraphQL Mesh as a "transport" layer between GraphQL Federation (which includes n subgraphs) and external sources, in my case it's a bunch of services that follow the next characteristics:

• Each service has its own needed HTTP headers and should be described within the GraphQL Mesh layer because I don't want to specify it from GraphQL Subgraphs.
• Service has n methods, each of which requires a different request body and should be set up within the GraphQL Mesh layer

How it looks:

1. A Subgraph makes a gql request to GraphQL Mesh with provided auth token (as an example) -> GraphQL Mesh knows itself what should be provided as a Body/Headers to X REST Service (X Service has 10 methods with different request body's)
2. B Subgraph makes a gql request to GraphQL Mesh with provided auth token (as an example) -> GraphQL Mesh knows itself what should be provided as a Body/Headers to Y REST Service (Y service has 10 methods with different request body's).

In other words, I don't want to configure something outside of the GraphQL Mesh related to external services, but to use it as a unification place for n services.

[ardatan]

As described in our documentation. You can do the following;

sources:
    - name: X
      handler:
         someHandler:
             # some config
             operationHeaders:
                  X-Header: "MY-TOKEN"
   - name: Y
     handler:
        someOtherHandler:
           # some other config
           operationHeaders:
               Y-Header: "MY-OTHER-TOKEN"

operationHeaders is different for each source.