We are currently trying to follow Vercel’s recommendations after the recent security incident, especially around protecting secrets more strictly.
Our setup is the following:
- We manage our environment variables in Doppler
- We use the Vercel <> Doppler integration to sync those environment variables from Doppler to Vercel
- In Doppler, those variables are configured as Restricted and are not visible there
However, after syncing them to Vercel, they appear as visible on click in the Vercel dashboard.
When we try to edit those environment variables in Vercel and mark them as Sensitive, we get this error:
You cannot change the type of an integration environment variable to sensitive
So the issue is: even though the secrets are protected in Doppler, once synced to Vercel we cannot make them Sensitive there, because they are managed by the integration.
Our questions are:
- Is this the expected behavior?
- Is there any supported way to keep Doppler as the source of truth and still have those synced variables treated as Sensitive in Vercel?
- If not, could this be supported as a feature request?
It would be useful if either:
- integrations could create environment variables as Sensitive by default, or
- Vercel allowed changing integration-managed variables to Sensitive without breaking the integration
Thanks.