Skip to content
Unexpected staged value change when sealing a secret
cross26work-commits
OP

a month ago

Hello Railway Support,

I am preparing to deploy Profit Radar to Railway Production and encountered an unexpected staged change while attempting to seal a sensitive environment variable.

Environment:

  • Project: Profit Radar Production
  • Service: Backend
  • Environment: Production
  • Variable: SUPABASE_SERVICE_ROLE_KEY

Issue:

The variable currently exists with isSealed=false.

After using the Seal option in the Railway Dashboard, a staged change appeared.

A read-only API inspection confirmed:

  • Status: STAGED
  • Patch target: SUPABASE_SERVICE_ROLE_KEY/value
  • Exactly one field is present in the patch.
  • No isSealed field appears in the patch.

The secret value was not decrypted or displayed. Therefore, I cannot determine whether the staged patch represents a Seal-only operation or an actual change to the secret value.

Questions:

  1. Is this expected behavior when sealing an existing variable?
  2. How can I verify that the existing secret value will remain unchanged without exposing it?
  3. What is the safe procedure for resolving this staged change without deploying the application?
  4. Can the variable be sealed without changing its current value?

I have NOT applied or discarded the staged change, re-entered the secret, or attempted to seal it again.

Please provide an official, safe recovery procedure.

Thank you.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

The Seal option stages only the sealed flag for that variable. It does not re-enter or rewrite the stored value, so applying that change seals SUPABASE_SERVICE_ROLE_KEY and keeps its current value.

If you want to be certain before anything is applied, discarding the staged change is the safe option. Discarding only clears the pending patch, and the variable stays as it is now, unsealed, with its original value. You can then choose Seal again from the variable's 3-dot menu whenever you're ready.

Keep in mind that a sealed variable cannot be un-sealed. Once it is sealed, its value is still passed to builds and deployments, but it is never shown in the dashboard and can't be read back through the API. More detail is in our sealed variables docs.


Status changed to Awaiting User Response Railway • about 1 month ago


cross26work-commits
OP

a month ago

Hello Railway Support,

I need help safely sealing the existing SUPABASE_SERVICE_ROLE_KEY variable in my production Backend service.

The variable is currently applied but unsealed, with zero staged changes.

Previously, selecting Seal unexpectedly showed a staged change involving "value". I discarded that change.

Could a human support engineer please confirm:

  1. How can I seal this variable without changing its existing value?
  2. Why did a staged "value" change appear?
  3. Will applying Seal trigger a redeployment?
  4. How can I safely verify the value is preserved without exposing the secret?

Please provide the exact steps.

Thank you.


Status changed to Awaiting Railway Response Railway • about 1 month ago


Railway
BOT

a month ago

To seal the variable, open the Backend service's Variables in the Production environment, choose Seal from the variable's 3-dot menu, then apply the staged change. Sealing doesn't involve re-entering the secret. The Seal action stages only the sealed flag for that variable and leaves the value field out entirely, so applying it keeps your existing value.

A sealed-flag change also doesn't trigger a redeploy. Your service picks up the sealed variable on its next deployment, with the same value it uses today.

We can't pin down where the staged change you saw came from. A pending edit to the variable's value is a different change from a seal, and the patch you inspected matched a value edit (it targeted the value with no sealed flag). Since you discarded it, the variable kept its original value. Before you apply this time, look at the staged change and confirm it only marks the variable as sealed and doesn't touch the value. If it shows a value change again, discard it instead of applying.

There's no way to compare a secret's value without revealing it, and after sealing it can't be read back in the dashboard or through the API. So the safest check is to look at the variable just before you seal: confirm it's applied and unsealed with no staged edits, and do nothing else to it besides Seal. Sealing can't be undone. More detail is in our sealed variables docs.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

24 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 • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...