Update upgrade_notes to mention fail fast on workflows #1024
Conversation
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
Member
|
@emptywee any thoughts here? |
|
Yes, sounds good. Would be better if we had a choice in how we want the engine to behave (like I proposed to have |
m4dcoder
requested changes
Oct 8, 2020
Contributor
m4dcoder
left a comment
m4dcoder
left a comment
There was a problem hiding this comment.
I don't know why this specific feature deserves a mention in the upgrade notes. There are other Mistral -> Orquesta nuance that users should be aware as well. Why not just ask users to review the orquesta documentation in general?
m4dcoder
approved these changes
Oct 8, 2020
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.
Included a comment on upgrade notes about fail-fast on orquesta workflows.
Designed to explain the confusion on when workflows stop, raised in StackStorm/st2#5031.