Hi there,
I am upgrading my cloud functions from 1.1.2 to 1.4.3. In the "old" functions one could use the function variables like APPWRITE_FUNCTION_JWT or APPWRITE_FUNCTION_USER_ID. Do these, now environment variables, still exist or do I need to pass those information's myself?
Hey there 👋 Information that used to be in env variables and is not static was moved to headers. For example, function ID stayed as env var, as that never changes. But user ID and JWT are different with every request, so those are now headers. Here you can check all that Appwrite provides for you: https://appwrite.io/docs/functions-develop#headers
In your scenario you are looking for context.req.headers['x-appwrite-user-id'] and context.req.headers['x-appwrite-user-jwt'].
Yes! Thats what I was looking for, thank you! <:appwriteheart2:1073243188954935387>
<:appwriteheart2:946074073627246692>
[SOLVED] 1.4 Function JWT token
Recommended threads
- Bug: Cloud Function On Schedule Didn't R...
Heya I have a cloud function with this cron `0 17 * * *` to run at 9AM PT every day. I have not touched this since I set it up, and it has been working fine s...
- functions
Code for function not being created in Github. Permissions are set correctly, repository is created, however no code is in the created repository. Just trying...
- Error 400: redirect_uri_mismatch
Hi team, Google OAuth was working fine with our Appwrite Cloud setup until yesterday. We did not change any configuration in Appwrite, Google Cloud, or our cod...