17 days ago
If skipDeploys=true commits the new region without starting a replica, will deploymentRestart on the existing stopped deployment use its original immutable us-west2 configuration, or the newly committed europe-west4-drams3a service configuration?
If it uses the original deployment configuration, what is the officially supported operation to create the first Amsterdam deployment while keeping the application stopped until after the attached volume has been migrated and verified byte-for-byte?
1 Replies
17 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 17 days ago
17 days ago
Restarting existing stopped deployment will use the same region where its deployed before
You can't migrate volume with application stopped, You need to create a new deployment to trigger Volume migration, Volume migration will copy the data to the new region before starting the application on the new region