Document migration endpoints and S2S Proxy setup for multiple self-hosted servers - #5043
Open
lukeknep wants to merge 4 commits into
Open
Document migration endpoints and S2S Proxy setup for multiple self-hosted servers#5043lukeknep wants to merge 4 commits into
lukeknep wants to merge 4 commits into
Conversation
Document that a migration endpoint pairs exactly one self-hosted server with one migration server, and that a single migration server can hold multiple endpoints. This allows several self-hosted S2S Proxy deployments to connect to the same migration server and migrate Namespaces in parallel, provided each self-hosted server has a unique cluster name and Initial Failover Version. Replaces the partial description in Limitations with a pointer to the new section, and adds an FAQ entry for the question as customers ask it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| Tell Temporal how many self-hosted servers you plan to migrate from and whether those migrations run in parallel, so | ||
| that the correct number of endpoints and migration servers can be provisioned. | ||
|
|
||
| ### S2S Proxy configuration |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'S2S Proxy configuration' should use sentence-style capitalization.
Contributor
📖 Docs PR preview links
|
Drop the description of multiple endpoints residing on one cloud-side migration server, which is internal configuration customers neither control nor need. Frame the guidance around what the customer does: one S2S Proxy deployment and one migration endpoint per self-hosted server, with unique cluster names and Initial Failover Versions when migrating from several servers at once. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
lukeknep
changed the title
Readers were pointing the connectivity test at a cloud-side address, and the page only answered parallelism for multiple self-hosted servers, not for multiple Namespaces on one server. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents how migration endpoints and S2S Proxy deployments map to self-hosted servers in Automated migration.
Why
A customer migrating separate development and production Temporal Services asked whether they could run those migrations in parallel. The answer is yes, but the docs never explained how endpoints and proxies map to self-hosted servers, so the assumption from the field was that only one server could be connected at a time. The existing Limitations bullet covered the collision case only and omitted the Initial Failover Version requirement.
The guidance is written from the customer's side of the connection. Cloud-side provisioning details are deliberately left out; customers are asked to tell Temporal how many servers they are migrating from and whether those migrations run in parallel.
Testing
yarn buildpasses with no new warnings.🤖 Generated with Claude Code