Add breaking changes docs for input-elasticsearch #16744
Merged
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
|
📃 DOCS PREVIEW ✨ https://logstash_bk_16744.docs-preview.app.elstc.co/diff |
robbavey
requested changes
Dec 3, 2024
| ==== |
There was a problem hiding this comment.
Maybe put these before the HTTP output - I think it might make sense to order these alphabetically
(cc @karenzone)
| [cols="<,<",options="header",] | ||
| |======================================================================= | ||
| |Setting|Replaced by |
There was a problem hiding this comment.
Do we want these in alphabetical order?
This commit follows the pattern established in elastic#16701 for indicating obsolete ssl settings in logstash core plugins.
donoghuc
force-pushed
the
ssl-obsolete-input-elasticsearch
branch
from
d3f1645 to
f54f9ff
Compare
|
📃 DOCS PREVIEW ✨ https://logstash_bk_16744.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?
This commit follows the pattern established in #16701 for indicating obsolete ssl settings in logstash core plugins.