environment context variables do not override build variables

[naipath]

If you define environment variables in the netlify.toml only the build.environment variables are being used.

Eg:

[build.environment]
  GREETING="Hello World! I am a variable set in a .env file"

# When building on the production environment this variable will NOT be used.
[context.production.environment]
  GREETING="production greeting"

[swyxio]

hi Naipath, i've checked with our support and unfortunately this is a bug in our platform. :(

The fix is to set the environment variable inside the app.netlify.com UI itself.

This is totally on us. Sorry. The requisite bug report has been filed.

[nesymno]

@sw-yx but if I need them? I need them to separate prod and stage environment. May be you know a way to do this?

[swyxio]

yes @weijinnx, you set up the env variables inside the app.netlify.com UI itself. netlify also provides you extra variables you can use inside your code: https://www.netlify.com/docs/continuous-deployment/#build-environment-variables

[shmargum]

Hi, I see that this issue was closed, but was it resolved?
I am having similar issues when trying to use environment variables for deploy-preview in my lambda functions.

[swyxio]

i see this. now that im rereading this issue im not sure why our support thought this is a netlify functions issue. it looks like there is a related issue with deployed netlify functions reading environment variables, but possibly separate from this one.

if you deploy this does it work? so can we confirm that its just a netlify-lambda issue?

[8eecf0d2]

Afaict this is working as intended, the context when using netlify-lambda is not production, it could potentially be development or something, but the context needs to be set somewhere..

I might be forgetting but does netlify-lambda provide a cli argument to set the context and or is any context use by default?

[shmargum]

yup, the branch fixes it for me 👍

[shmargum]

my use case is for [context.deploy-preview.environment] and [context.branch-deploy.environment]

[shmargum]

@8eecf0d2 the context gets set automatically by netlify;
for production is [context.production]
for pull requests/deploy previews: [context.deploy-preview]
for all branch deploys: [context.branch-deploy]
and for a specific branch: [context.name-of-my-custom-branch]

[8eecf0d2]

@shmargum right, I was talking about netlify-lambda which afaict doesn't set the context.