-
Notifications
You must be signed in to change notification settings - Fork 10k
Clarify expected interaction between Worker Versions and Durable Obje… #20762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify expected interaction between Worker Versions and Durable Obje… #20762
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryClarified the expected interaction between Worker Versions and Durable Objects migrations, enhancing the documentation for better understanding.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add What is Hyperlint?Hyperlint is an AI agent that helps you write, edit, and maintain your documentation. Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation. |
|
|
||
| In order to limit the blast radius of Durable Object migration deployments, migrations should be deployed independently of other code changes. | ||
|
|
||
| To understand why Durable Object migrations are atomic operations, consider the hypothetical example of gradually deploying a delete migration. If a delete migration were applied to 50% of Durable Object instances, then Workers requesting those Durable Object instances would fail because they would have been deleted. To do this without producing errors, a version of the Worker which does not depend on any Durable Object instances would have to have already been rolled out. At which point you can deploy a delete migration without affecting any traffic and there is no reason to do so gradually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is good explainer to have and point ppl back to 🙌
src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx
Outdated
Show resolved
Hide resolved
…s/gradual-deployments.mdx
src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx
Outdated
Show resolved
Hide resolved
…s/gradual-deployments.mdx
|
Now tracking here #21677 |
…cts migrations
Summary
Screenshots (optional)
Documentation checklist