3 hours ago
Please route this to the team maintaining Railway’s Vercel integration.
We use Railway as the verified configuration source and sync variables into Vercel. Vercel flags credential-like integration-managed variables as Config / Needs Attention. We need a supported migration to Vercel Secrets that retains the existing values, automatic Railway synchronization, and every current environment target.
Reproduction: an authenticated owner sent PATCH /v9/projects/{projectId}/env/{envId} with only {"type":"sensitive","visibility":"secret"}. Vercel returned HTTP 400: "You cannot change the type of an integration Environment Variable to Sensitive." A September 21 test using Vercel’s own editor returned the same error. Neither managed-variable change was accepted. The equivalent conversion succeeded for four unmanaged variables.
A September 17 audit counted 68 affected managed entries across three projects. Newer entries also show this warning; 68 is a historical count, not a current exact total. We have not established an outage or credential compromise from these classification warnings.
Vercel’s support assistant referred us to the integration provider and declined human escalation. That assistant response is not a human-confirmed technical guarantee.
Please confirm:
- Can Railway’s current Vercel integration provision and keep variables as Vercel Secrets?
- Is an existing-setting or provider migration available, or is an integration code change required?
- What procedure preserves source values, Production/Preview/Development targets, branch overrides, custom environments, and automatic sync?
- How should we test one controlled entry, verify the next Railway sync does not revert it, and roll back if needed?
Please do not uninstall the integration, disable sync, delete variables, rotate credentials, change scopes, or redeploy production as a diagnostic action. We need the supported procedure first. No credential values or private project/integration identifiers are included here. We can provide specific identifiers through this private support thread if needed.
Thank you,
Theodore Schiele
0 Threads mention this feature
1 Replies
3 hours ago
We checked our documentation and it does not cover this yet, so the Railway community is the best place to get a real answer: people who have already worked this out on their own projects and can tell you what actually worked.
So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • about 3 hours ago