Cannot set Integration Environment Variables to Sensitive
@jacobparis
·
2026-04-21
·
via Vercel Community - Latest posts
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 be the source of truth, but hopefully it’s acceptable as a stop-gap until we have the proper feature shipped
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。