-
Notifications
You must be signed in to change notification settings - Fork 67
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
fix(elastic): rename ssl options to tls #181
Conversation
I would update package elasticsearch-js to last version, because last version supported Node.js 16 and more |
@mcollina check PR |
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
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.
This is a semver major change.
@mcollina and @jsumners Hi guys, how about this PR? pino-elasticsearch v7.0.0 is broken, https connection doesn't work. After updating the package @elastic/elasticsearch to version 8.0.0, because in version 8 renamed the ssl option to tls - Rename ssl option to tls |
I would say that this PR should be backward compatible so that it is easier to merge and release. But I really don't have any strong opinion on the module in general. I was just pointing out that the current change will require publishing a major. |
I can update and use two params (ssl and tls) and mark ssl as deprecated |
I have no issue in shipping a major. This sits in the 300+ notification queue (currently on mobile). |
#180 In version 8 renamed the ssl option to tls.
This commit adjusts the code to reflect this change, ensuring compatibility with Elasticsearch 8.
Rename ssl option to tls
Link to documentation