Per-branch environment variables (=secrets)

[gualter]

Hello @0xsoji

The process we outline in this thread mostly focus on having the access tokens as variables in the UI, and then reuse them depending on the context. Here is a great explanation of what we mean:

Netlify.toml context env variables do not apply to functions

There is a workaround It’s to have a more intelligent build script that selects the appropriate variables to use during build. One can use contexts to choose a different build command, so something like this (untested) is what I might use: in the UI, set $STAGING_ENDPOINT and $PRODUCTION_ENDPOINT to different values in netlify.toml use build commands like this to incorporate them: [context.staging] command = "./my-production-build-script.sh" [context.production] command =…

The idea is for you to keep the variables stored safely on the UI and call specific scripts (which export the correct token, per context)

Let me know if this helps!