Dynamic Endpoint URI Not Working

[wasurdev]

Hello, I am attempting to place a dynamic URL in the meshrc.yaml configuration file as follows:

sources:
  - name: MyGraphQL
    handler:
      graphql:
        endpoint: "{env.MY_ENV_VARIABLE}"

However, this and any variation I have tried is not working. Interestingly, this exact same syntax IS working for both operation and schema headers.

I am running mesh with a --require dotenv/config command to load dotenv variables.

Thank you!

[santino]

Have you tried endpoint: ${MY_ENV_VARIABLE}?

This is the syntax I am using and it's working fine for me.
If it doesn't work, try to log process.env.MY_ENV_VARIABLE in your index.js or server.js (depending on what you have); to make sure the variable is set in the process.

[wasurdev]

Scratch that - the environment variable didn't need to be preceded by 'env' as it did with the others..

Appreciate your response! Resolved!

[ardatan]

But ${ENV_VAR} will embed the value into the raw configuration and in the artifacts you won't be able to change it anymore.

[santino]

@ardatan is right.

I overlooked this change in the newest graphql-mesh releases.
If you use the syntax I shared above, preceded by the dollar sign $, the value of the variable will be hardcoded into the Mesh artifacts.
Effectively this defeats the purpose of environment variables, and you won't be able to use your build across different environments.

The syntax you need to use is:
endpoint: "{env.MY_ENV_VARIABLE}"

The env. prefix is required, as Mesh will use this to understand it dynamically needs to inject the value for the environment variable.

Let us know If that still doesn't work.
Maybe there is something wrong with the way you're setting these variables with dotenv.
I also use dotenv and things are working properly for me, so I trust you will be able to get this working.

[wasurdev]

Thank you for the replies - and sorry for the delay on a response.

@santino, that syntax is not working for me.

ENV file example:
ACCOUNTS_URN = http://localhost:4001/graphql

MeshRC:

sources:
  - name: Accounts
    handler:
      graphql:
        endpoint: "{env.ACCOUNTS_URN}"

Command:
mesh dev --require dotenv/config

Error:
Mesh: Only absolute URLs are supported

[xmlking]

Have you tried with single quotes endpoint: ‘{env.ACCOUNTS_URN}’? and mesh build -r dotenv/config?

[MM3y3r]

Was this issue resolved? I cannot use dynamic env vars either it seems.

[ardatan]

Could you create a new issue with a reproduction on CodeSandbox or StackBlitz?

[MM3y3r]

I created #4191 and added some more of my code. I will try to expand the example..

[ardatan]

We need a reproduction on CodeSandbox or StackBlitz in order to help you. Thanks.

[MM3y3r]

Just FYI in my case the problem originated with docker/kubernetes and was therefore unrelated to this tool. Be aware that env vars are not available during build step.

[noe-lc]

Hey @MM3y3r, I just had this problem while trying to deploy with Docket and K8S. Wondering if you could find a workaround?

[xmlking]

Just FYI in my case the problem originated with docker/kubernetes and was therefore unrelated to this tool. Be aware that env vars are not available during build step.

Can we use mesh build -r dotenv/config To make env variables available at build time ?
I also noticed endpoint supplied via env for graphQL handler is flaky. It worked for me for query/mutation but not for subscription