This repository was archived by the owner on Dec 20, 2024. It is now read-only.
Sensitive Environment Variables appear encrypted in server functions when accompanied by a comment #5898
Replies: 1 comment
|
Thanks for reporting this! The engineering team identified the cause and deployed a fix. 🙇 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Page to Investigate
Vercel > Project Settings > Environment Variables
Description
When creating a sensitive environment variable without a comment, the name and value are readable within a server function (Node.js). However, after adding a comment to the sensitive environment variable and redeploying the app, the API key becomes unreadable, as if it were encrypted, and not being properly decrypted for use in the server function.
Steps to Reproduce
Workaround
The temporary workaround is to remove the sensitive environment variables with comments, re-add them without comments, and redeploy the app.
Please let me know if you need any more info 😄
All reactions