My last deployment failed with this error:

03:56:35: Deploying functions
03:57:50: couldn't create lambda code for /owner-invoice

The lambda worked locally. Then I commented out that lambda and I received:

03:59:56: Deploying functions
04:01:09: couldn't update lambda code for /booking-alert/listen
04:01:10: Deployment completed with status FAILED

Is something down?

I'm stuck and since my migrations were applied to the DB, the app is not working correctly ATM

@lipchyk can you please check the error logs for the function deployments?

Hi. I can see the following in the log

InvalidParameterValueException: Lambda was unable to configure your environment variables because the environment variables you have provided exceeded the 4KB limit

that's strange because I haven't changed anything in the env vars

maybe it's huge GCLOUD_PRIVATE_KEY value?

ah I probably know… we recently started to include more envs, like NHOST_SUBDOMAIN, NHOST_HASURA_URL, etc…

so previously it worked for you and now the total amount exceeded 4Kb

I'll try to remove a few

it worked, thanks

anyway, thanks for reporting. This is kinda unexpected for us as well

@lipchyk Is that a hard limit from AWS? The 4KB?

apparently, it's a hard limit from AWS - https://aws.amazon.com/premiumsupport/knowledge-center/lambda-environment-variable-size/

@Szilard 👆 about the issue/pr for the Dashboard regarding env var length

we should take into account that our build system (watchtower) populates extra envs (that's basically the reason why it happened for kratam just now, because we introduced it just recently)

@lipchyk Should we pass this error message to the deployment logs? So instead of only showing "couldn't update lambda code" we can also explain why?

I think there should be 2 separate sets of env vars: one for the deployment process and one for the functions

E.g. one might need a secret key to access private repositories during the build process but not when running the lambda.

That's an interesting suggestion.