Environment variable drift after promoting Railway preview deployments

Preview promotion variable reconciliation

Railway preview deployments provision isolated service instances with distinct credentials, allowing integration testing without production secrets. When a preview deployment is promoted to production, the platform does not automatically reconcile environment variable differences between the preview and production environments.

Variables added or modified in the preview environment remain absent from production unless manually copied. The CLI provides railway variables --json output for each environment but includes no built-in diff or sync command to detect or resolve drift.

Specific questions

• What is the expected workflow for ensuring variable parity when promoting a preview deployment to production?
• Are there documented patterns or tooling for automating variable comparison across Railway environments?
• Does Railway plan to introduce native variable reconciliation or diff capabilities during promotion?