Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📖 Docs PR preview links
|
|
|
||
| This is a complex question. The answer depends on your specific situation. The most common considerations are: | ||
|
|
||
| 1. Risk of change - No matter what, clients must be updated to use the new cloud-side Namespace. The big difference is that |
There was a problem hiding this comment.
This #1 is unclear to me. Are you saying "Automated Migration gives you the flexibility to migrate Workers in different orders / space it out over time, instead of 'all at once' ?"
|
|
||
| ## Frequently asked questions | ||
|
|
||
| ### When should I opt for auto migration? |
There was a problem hiding this comment.
I do not think the answer here addresses this question.
| ### Can I split Workflows from a single source Namespace into multiple cloud-side Namespaces? | ||
|
|
||
| Not directly. The migration tooling migrates all Workflows from a Namespace. If your goal is to split Workflows, then you should | ||
| manually migrate any workflows into their new cloud-side targets prior to starting an auto-migration. |
There was a problem hiding this comment.
Can we link to a docs page about how to "manually migrate a workflow" ?
|
|
||
| ### Can I combine manual and auto migration? | ||
|
|
||
| It depends. Auto migration requires a "fresh" target cloud-side Namespace (e.g. one that has never had a running Workflow). |
There was a problem hiding this comment.
I would suggest this, to make it more clear:
You can, as long as the automated migration comes first. Automated migrations require a brand new Temporal Cloud Namespace. An automated migration cannot be run against a Namespace that already has running Workflows, even if those Workflows were manually migrated from your cluster.
| ### What Workflows are migrated by default? | ||
|
|
||
| All Workflows are migrated by default. For closed Workflows, you may specify a date range to be migrated. Limiting the time range for | ||
| closed Workflows will greatly reduce the amount of time it takes to migrate a Namespace. Your cloud-side Namespace must |
There was a problem hiding this comment.
Suggested additional FAQ: "What affects the amount of time a migration takes?" or "How can I speed up a migration?"
|
|
||
| ### I have a long retention period for my Workflows. Is this compatible with Temporal Cloud? | ||
|
|
||
| Occasionally, self-hosted [retention periods](/temporal-service/temporal-server#retention-period) are in excess of what |
There was a problem hiding this comment.
Do we ever spell out the max retention period we support for migrations?
|
|
||
| ### I would like to enable payload encryption as part of the migration. Is this supported? | ||
|
|
||
| Enabling payload encryption as part of the migration is not currently supported. If encryption is required, then the best |
There was a problem hiding this comment.
Suggested rewrite: "The automated migration tooling cannot add payload encryption. To encrypt payloads sent to Temporal Cloud, you must encrypt payloads in your cluster before starting the automated migration process."
3 participants
What does this PR do?
Updates to FAQ + some misc corrections.
┆Attachments: EDU-6175 faq and misc updates