-
Notifications
You must be signed in to change notification settings - Fork 39
Add new engine command named "continue" #172
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
Conversation
Add a new engine command named "continue". Previously, the default value when `do` is not specified is `noop`. When the previous task state is one of the failure states, noop will be assumed as remediation and the workflow execution will succeed. With `continue`, it will be replaced as the default value when `do` is not specified. The workflow en 8000 gine will not alter the previous task state and will continue to conduct the workflow execution. If the previous task state is one of the failure states, the conductor will continue and fail the workflow execution.
Add unit test to make sure when "do" is not specified and the task failed, the workflow execution will continue with failure.
The `continue` engine command replaces `noop` as default value when `do` is not specified. Replace `noop` with `continue` in the expected task sequence.
Add the `continue` command to the list of engine commands. Update the description to explain the difference between `noop` and `continue`.
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 a new behavior for orquesta
workflow, is there a plan to create new example workflow and integration testcase in st2
?
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.
Looks good, but (AIUI) it needs an additional test for noop
transitions, and a few other small tweaks.
ba37202
to
c8ad8fd
Compare
Codecov Report
@@ Coverage Diff @@
## master #172 +/- ##
==========================================
+ Coverage 94.22% 94.25% +0.02%
==========================================
Files 40 40
Lines 2461 2470 +9
Branches 470 471 +1
==========================================
+ Hits 2319 2328 +9
Misses 84 84
Partials 58 58
Continue to review full report at Codecov.
|
Add more workflow examples to illustrate the use of continue, noop, and the fail engine commands.
Add unit tests to cover various error handling use cases with continue, noop, and fail engine commands.
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.
LGTM
Add a new engine command named "continue". Previously, the default value when
do
is not specified isnoop
. When the previous task state is one of the failure states, noop will be assumed as remediation and the workflow execution will succeed. Instead of changing the behavior ofnoop
, introduce a new command namedcontinue
. Withcontinue
, it will be replaced as the default value whendo
is not specified. The workflow engine will not alter the previous task state and will continue to conduct the workflow execution. If the previous task state is one of the failure states, the conductor will continue and fail the workflow execution. Fixes StackStorm/st2#4740.