[DOC] Describe how to upgrade Logstash managed by package manager in case were installed not supported plugins #15317
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
…ith a release, during an upgrade package.
|
📃 DOCS PREVIEW ✨ https://logstash_15317.docs-preview.app.elstc.co/diff |
…re installed plugins not officially supported
andsel
changed the title
|
📃 DOCS PREVIEW ✨ https://logstash_15317.docs-preview.app.elstc.co/diff |
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.
Release notes
[rn:skip]
What does this PR do?
Updates the deb/rpm upgrade flow describing how to behave when the installation was customized with not officially supported plugins.
Why is it important/What is the impact to the user?
If the user customize a Logstash installlation, installing plugins which aren't part of the distribution, the upgrade process applied by the system package manager, overwriting Logstash installation also erase those plugins.
The user is guided how to upgrade in such cases.
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs