-
Notifications
You must be signed in to change notification settings - Fork 142
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
Allow Insecure HTTPS #2913
Allow Insecure HTTPS #2913
Conversation
Added instructions to enable SSL
💚 CLA has been signed |
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.
Great job @kmitul thank you for looking into this 👍 I’ve left a couple of small suggestions. The main concern is highlighting that we don’t want this setting to be used in production, so the comments should be adjusted accordingly.
Also, please make sure you sign the contributor agreement, as we can’t merge your PR without it.
buildkite test this |
You need to run |
Hi @jedrazb :) |
buildkite test this |
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! Thank you for contributing to the repo :)
Awesome stuff. Make sure to check out our contributor program, to get rewards! https://www.elastic.co/community/contributor/submissions |
buildkite test this |
buildkite test this |
💔 Failed to create backport PR(s)The backport operation could not be completed due to the following error: The backport PRs will be merged automatically after passing CI. To backport manually run: |
(cherry picked from commit ece146e)
(cherry picked from commit ece146e)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Closes #2491
Updated the verification logic for server certificates to allow for configurable settings. The
verify_certs
option now defaults toTrue
but can be set toFalse
in the configuration. This change enhances flexibility, allowing users to opt out of certificate verification in environments with varying security requirements.Checklists
Pre-Review Checklist
config.yml.example
)Changes Requiring Extra Attention
Release Note