17 minutes ago
Hello Railway Support,
We completed your recommended disposable-environment test successfully.
An explicit worker-only environmentPatchCommit with skipDeploys:true preserved the unrelated staged sentinel, including its patch ID, timestamp and SHA-256, after settlement. No deployment occurred.
Our real TLM staging environment now has 16 pending changes, including eight unrelated Amazon variables, one service creation and seven backup-worker fields.
The worker-only commit must include a pinned GHCR image, encrypted registry credentials and a JIT variable seal.
However, the Railway API masks these protected values.
How can we safely commit only the worker changes while preserving all unrelated pending changes and their encrypted values?
Please provide the exact supported API procedure. We must not apply the entire staged patch.
Thank you.
1 Reply
16 minutes ago
The staged-changes commit in our public API, environmentPatchCommitStaged, applies an environment's entire staged changeset. We can't give you a confirmed procedure for committing a worker-only patch that carries a pinned image, registry credentials and a sealed variable while leaving the other staged changes and their encrypted values untouched.
Your disposable-environment result is the best evidence for that workflow. Before running it against your TLM staging environment, repeat the test in a disposable environment with the exact worker patch you plan to use, including the registry credentials and sealed variable, and confirm the unrelated staged sentinel is still preserved afterwards.
Status changed to Awaiting User Response Railway • 16 minutes ago
Status changed to Solved kokaalbin-oss • 15 minutes ago