Cannot change the type of an integration Environment Variable to Sensitive.

[amyegan]

We’re working on it and Jacob shared a temporary workaround

Cannot set Integration Environment Variables to Sensitive

Thanks for reporting, our integrations team is actively working on this feature but since it involves adding support for each third party, we can’t give an immediate ETA for when it will be enabled on the Doppler integration In the meantime, the fastest workaround to de-sync is to use vercel env pull .env.temp to pull non-sensitive env vars into a file, then you can copy/paste them into the “add new environment variable” flow and mark as sensitive This isn’t ideal since doppler will no longer …