Skip to content
Production security key rotation blocked — canRedeploy=false
darrius07
OP

23 days ago

Subject: Production security key rotation blocked — canRedeploy=false on active CLI deployment

Hello Railway Support,

We need help completing an urgent credential rotation following the October 21 security incident, without changing our production application code.

Service details

  • Project: pfas-data-bridge-api-staging
  • Environment: production
  • Service: pfas-data-bridge-api
  • Active deployment: 9f0f82e0-8082-475c-be97-072dbb3148c8
  • Deployment status: SUCCESS
  • Active image digest: sha256:ca9482fb853a307fd1cd23c3e7d66db158d12c3f309ab6aa65bad1c045a2195f

Verified state

  • The replacement OpenAI credential has been saved in the service variable OPEN_AI_API.
  • There are no pending configuration changes.
  • OPEN_AI_API is the only application variable differing between the saved configuration and the active deployment snapshot.
  • All other variables are unchanged, including database credentials and CONNECTOR_SECRETS_KEY.
  • The application is healthy (GET /health returns HTTP 200).
  • Railway reports canRedeploy: false for the active deployment.
  • The dashboard does not offer a Redeploy action.
  • No production changes have been performed during this investigation.

What we need

Please confirm the officially supported procedure for launching a new deployment using the exact existing production image and the currently saved environment variables.

We must not deploy the latest GitHub commit, rebuild from potentially different source code, restore old secrets through rollback, or modify any other application configuration.

If reusing this exact image is impossible, please explain the safest supported alternative and its consequences before we proceed.

Please do not initiate changes to our production service without our explicit approval.

Thank you.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 23 days ago


sam-a
EMPLOYEE

23 days ago

There isn’t a supported way to launch this deployment’s exact existing image with updated variables. This deployment can’t currently be redeployed, and restarting it won’t load the replacement OPEN_AI_API value.

The safest supported alternative is to run railway up from a verified copy of the exact source used for production, with dependencies pinned. This uploads your local source rather than pulling the latest GitHub commit and uses the currently saved variables, but it creates a new image whose digest can differ even when the application code is unchanged.

We haven’t changed your production service. Before proceeding, you’ll need to verify that source copy and accept the new build.


Status changed to Awaiting User Response Railway • 23 days ago


Railway
BOT

16 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 16 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...