Documentation Index
Fetch the complete documentation index at: https://docs.envsecrets.com/llms.txt
Use this file to discover all available pages before exploring further.
Setup
- Go to integrations catalog in your envsecrets dashboard and choose “Vercel.”
- Complete the Oauth procedure that begins and grant access to all of your Vercel application to which you wish to sync your secrets.
Activation
- Go to the integrations dashboard in your envsecrets organisation and under “Vercel” choose “Sync New Environment With Your Vercel Account.”
- In the page that opens, select your envsecrets project, environment and your Vercel application where you wish to push/sync your secrets.
- Complete and save the form.
Usage
Platform
- Navigate to the environment for which you activated the integration.
- Click on the “Sync” button.
- Choose the Vercel application to which you want to sync your secrets.
- Approve the sync.
CLI
- Use the command:
envs sync --env [name-of-your-remote-environment] - Choose the Vercel integration.
Reserved Environment Variables
The following secrets/variables cannot be forward-synced to Vercel because they are reserved for Vercel’s runtime:- AWS_REGION
- AWS_DEFAULT_REGION
- AWS_ACCESS_KEY_ID
- AWS_SECRET_KEY
- AWS_SECRET_ACCESS_KEY
- AWS_EXECUTION_ENV
- AWS_LAMBDA_LOG_GROUP_NAME
- AWS_LAMBDA_LOG_STREAM_NAME
- AWS_LAMBDA_FUNCTION_NAME
- AWS_LAMBDA_FUNCTION_MEMORY_SIZE
- AWS_LAMBDA_FUNCTION_VERSION
- AWS_SESSION_TOKEN
- NOW_REGION
- TZ
- LAMBDA_TASK_ROOT
- LAMBDA_RUNTIME_DIR