-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add SSL Breaking changes for logstash-output-http to breaking changes… #16701
Conversation
I like the idea here. For all the other plugins we will continue with sections that have the plugin name and the obsolete parameters. Looks like the docs build is red. The only thing I saw in the logs is a warning about use of headers. Not sure if that is the cause. Once we get this base example sorted out we can start making sure the other plugins get a similar treatment :) |
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.
Left suggestions and broader guidelines inline.
Let's discuss and iterate. When we agree, let's apply these style guidelines for the other 10 plugins with changes to SSL settings.
Co-authored-by: Karen Metts <[email protected]>
Doc Preview: |
📃 DOCS PREVIEW ✨ https://logstash_bk_16701.docs-preview.app.elstc.co/diff |
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!
This commit follows the pattern established in elastic#16701 for indicating obsolete ssl settings in logstash core plugins.
This commit follows the pattern established in elastic#16701 for indicating obsolete ssl settings in logstash core plugins.
This commit follows the pattern established in #16701 for indicating obsolete ssl settings in logstash core plugins.
… doc
PREVIEW: https://logstash_bk_16701.docs-preview.app.elstc.co/guide/en/logstash/master/breaking-changes.html