Does changing region actually change the region?

[pksunkara]

I have tested it through both API and Terraform. Changing the region updates the service instance value to the new region in the UI (both in setting and deployment panel) but I don't see a new deployment happening. Going and clicking "Redeploy" is not actually migrating the volume, so I am not actually sure if it's deploying in the new region or not. But when changing the region through UI, a new deployment happens and volume is migrated.

Therefore, I have doubts whether the region shown in the UI is actually the region the service is being deployed.

1. If Railway doesn't want to actually update the region of the service through API: a. We need to trigger redeploy after updating region. b. Railway needs to fix the UI in the deployment panel showing the wrong region.
2. If Railway wants to support updating the region of the service through API: a. Railway needs to fix it.

Either way, I would love to know if anyone know of a way to test it through service logs to understand which region the service is actually deployed?

@wertlex Would love to know your experience of using terraform for regions.

@zuchka Can you please let me know which way to proceed forward?

Funding

• You can sponsor this specific effort via a Polar.sh pledge below
• We receive the pledge once the issue is completed & verified

[wertlex]

This is quite an interesting finding

I didn't dig deep enough:

• I checked that UI value has been changed
• did geo ip check for couple services facing public network (proxy ip was resolved to expected region)