Add force-continue-as-new signal to schedule workflow #5034
Conversation
This file contains 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
yiminc
approved these changes
Oct 28, 2023
rodrigozhou
pushed a commit
that referenced
this pull request
Oct 30, 2023
**What changed?** Add `force-continue-as-new` signal to schedule workflow, to force it to continue-as-new immediately. **Why?** This could be used to force all running schedules onto the newest version of the workflow code, to allow retiring older code paths. **How did you test it?** unit test
rodrigozhou
pushed a commit
that referenced
this pull request
Oct 31, 2023
**What changed?** Add `force-continue-as-new` signal to schedule workflow, to force it to continue-as-new immediately. **Why?** This could be used to force all running schedules onto the newest version of the workflow code, to allow retiring older code paths. **How did you test it?** unit test
rodrigozhou
pushed a commit
that referenced
this pull request
Nov 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 changed?
Add
force-continue-as-newsignal to schedule workflow, to force it to continue-as-new immediately.Why?
This could be used to force all running schedules onto the newest version of the workflow code, to allow retiring older code paths.
How did you test it?
unit test
Potential risks
Is hotfix candidate?