Use graph client with docker network based graph node

[rhlsthrm]

We are using a graph node as part of a fully-local setup:

https://github.com/connext/nxtp/blob/a0eb052ac0abb8b83821005f1c44dd8d2448a1fb/docker-compose.chains.yaml#L21

I want to be able to generate a graph client that can be used on resources within this docker network that talk to the graph node. The config for this would look like this:

https://github.com/connext/nxtp/blob/e0519f79172025770047e3aed5c7fa5796f6d56c/packages/adapters/subgraph/.graphclientrc.yml#L140

However I am not able to easily generate the client for this. When I try, it fails because the host cannot access this endpoint. If I use localhost, the container cannot access the graph node because it's not on localhost from the container's point of view. The workaround I used is to spin up a temporary container within the network that can do this. However this is not a feasible option for our devs to use.

Is there another way to generate the schema from a different URL but have the client use the provided URL for the queries?

[ardatan]

You can use string interpolation to give different values for endpoint;

endpoint: "{env.MY_ENDPOINT}"

So you will give different env var during the build, and use a different one in the docker container.

[rhlsthrm]

@ardatan this is perfect, thank you for this!

[base0010]

You can use string interpolation to give different values for endpoint;

endpoint: "{env.MY_ENDPOINT}"

So you will give different env var during the build, and use a different one in the docker container.

Tried this as mentioned and seemed to work fine for the generation step however at runtime we get this error,
💥 🕸️ Mesh TypeError: Only absolute URLs are supported at getNodeRequestOptions (/home/node/node_modules/node-fetch/lib/index.js:1327:9) .... is there another option or parameter we need to enable to get this to work @ardatan

[ardatan]

What do you provide in your env variable? Let's create a new issue with a reproduction please.

[rhlsthrm]

This was an issue on our end. We got it to work. Thank you!

[stefan-girlich]

i'm observing the following error when trying to use string interpolation.
@ardatan please let me know if you can spot the issue; otherwise i'd create a separate github issue. thx!

error

parameter resolves to empty string

stack trace

Failed to generate the schema Error: Failed to fetch introspection from : TypeError: Failed to parse URL from
    at new Request (project/node_modules/undici/lib/fetch/request.js:77:15)
    at Agent.fetch (project/node_modules/undici/lib/fetch/index.js:116:21)
    at fetch (project/node_modules/undici/index.js:95:22)
    at fetch (project/node_modules/@whatwg-node/fetch/dist/create-node-ponyfill.js:210:18)
    at project/node_modules/fetchache/index.js:30:36
    at async wrappedFetchFn (project/node_modules/@graphql-mesh/runtime/index.js:450:24)
    at async Object.getWithSet (project/node_modules/@graphql-mesh/store/index.js:160:38) {

context

• using endpoint: "${env.FOO}" in .graphclientrc.yml
• running FOO="https://example.com" yarn graphclient build

[ardatan]

It should be either ${FOO} or {env.FOO}
YAML Parser will embed the value so it won't be dynamic in ${FOO}
But {env.FOO} will be dynamic and can be changed following startups.

[stefan-girlich]

perfect, both options work for me and could be a valuable addition to the docs.

related question: in .graphclientrc.yml, i want to create 1-n sources entries programmatically, also using env vars. is there a syntactic construct which allows that? if not, i would simply create the entire file .graphclientrc.yml programmatically.

thanks so much for the quick answer, i highly appreciated it 💯