Add force and breaking options to ServiceDeployer for Restate 1.6+#88
Merged
Add force and breaking options to ServiceDeployer for Restate 1.6+#88
Conversation
…mpatibility With Restate 1.6 (API v3), the force parameter no longer defaults to true, causing deployments with breaking changes (like removing handlers) to fail. This adds two new options: - force (default: false): Allows breaking changes and overwrites existing deployments. - breaking (default: false): Allows breaking changes without overwriting existing deployments. Safer for evolving services while preserving in-flight invocations. When both are set, force takes precedence. BREAKING CHANGE: Deployments that remove handlers or make other breaking schema changes will now fail by default. Set force: true or breaking: true to allow such changes.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
With Restate 1.6 (API v3), the force parameter no longer defaults to true, causing deployments with breaking changes (like removing handlers) to fail.
This adds two new options:
When both are set, force takes precedence.
BREAKING CHANGE: Deployments that remove handlers or make other breaking schema changes will now fail against Restate 1.6 by default. Set force: true or breaking: true to allow such changes.