-
Notifications
You must be signed in to change notification settings - Fork 859
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
Enable Update Workflow by default #6385
Conversation
common/dynamicconfig/constants.go
Outdated
`FrontendEnableUpdateWorkflowExecutionAsyncAccepted enables the form of | ||
asynchronous workflow execution update that waits on the "Accepted" | ||
lifecycle stage. Default value is 'false'.`, | ||
asynchronous workflow execution update that waits on the "Accepted" lifecycle stage.`, |
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.
Suggest not using "asynchronous" in text to mean the variant of Update that waits for Accepted. In https://docs.temporal.io/encyclopedia/workflow-message-passing#for-write-requests all Update usage is classified as synchronous. cc @drewhoskins-temporal
I think the dynamic config entry name itself is not changeable.
@@ -902,10 +902,8 @@ used when the first cache layer has a miss. Requires server restart for change t | |||
|
|||
FrontendEnableUpdateWorkflowExecution = NewNamespaceBoolSetting( | |||
"frontend.enableUpdateWorkflowExecution", | |||
false, | |||
`FrontendEnableUpdateWorkflowExecution enables UpdateWorkflowExecution API in the frontend. | |||
The UpdateWorkflowExecution API has gone through rigorous testing efforts but this config's default is 'false' until the |
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.
rigorous testing efforts
this is very true!
What changed?
Enable Update Workflow (sync and async) by default.
Note that I'm leaving the flag and the code checks for now, in case we need to disable it again.
Why?
For public preview.
How did you test it?
Potential risks
Documentation
Is hotfix candidate?