Make config changes for 3.8 more visible #1155
Open
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
nzlosh
approved these changes
Dec 16, 2022
arm4b
reviewed
Dec 16, 2022
| See :doc:`purging old data documentation <troubleshooting/purging_old_data>` for further | ||
| information. | ||
|
|
||
| * StackStorm’s Workflow engine can now handle shutdown events more gracefully. | ||
| Two new configurations has been added to `st2.conf` in the `[workflow_engine]` section to have more granular control. |
There was a problem hiding this comment.
Upgrade notes are intended to list the changes that are really required for the user to be aware of when upgrading from one st2 version to another (schema changes, renames, breaking changes, OS changes, python version, etc)
New features and enhancements like this one are usually not mentioned in detail for "Upgrade Notes".
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.
Between the Upgrade page, Update nodes and Release Blog Post we have a lot of info spread on how to update, but neither of them paints a full picture.
This PR makes the config changes for 3.8 more visible in the upgrade notes.