-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting lambda env variables does not work. #500
Comments
I don't know what you mean by "Lambda does not have these environment variables set." Zappa environment variables have existed long before "Lambda environment variables", which I think were only added last week. They're not the same thing, and I don't know how the two interact. Can somebody confirm this? Maybe your AWS environment variables are overriding the Zappa ones, but I don't see how that's possible. I think this more likely due to there being no APIGW than AWS Env, but needs investigation. |
I expected the |
You mean the AWS ones? |
If we do add support for those, it'll likely be done in a vendor prefixed way, ex |
Cannot confirm yet, still investigating. |
Confirmed it works with and without API Gateway, feel free to ask me to reopen if you can provide steps to reproduce. |
I am testing zappa for deployment of event-driven lambda functions (no APIGW component) and ran into trouble with env variables. According to documentation,
zappa_settings.json
like thisshould set two environment variables for the lambda,
NICE
andSEE
. However, the lambda does not have these environment variables set, as verified by bothprint(os.environ)
and looking at the lambda in AWS management console. Adding an environment variable manually works.The text was updated successfully, but these errors were encountered: