|
1 | 1 | [[changelog-client]]
|
2 | 2 | == Release notes
|
3 | 3 |
|
| 4 | +[discrete] |
| 5 | +=== 7.15.0 |
| 6 | + |
| 7 | +[discrete] |
| 8 | +==== Features |
| 9 | + |
| 10 | +[discrete] |
| 11 | +===== Support for Elasticsearch `v7.15` |
| 12 | + |
| 13 | +You can find all the API changes |
| 14 | +https://www.elastic.co/guide/en/elasticsearch/reference/7.14/release-notes-7.15.0.html[here]. |
| 15 | + |
| 16 | +[discrete] |
| 17 | +===== Support mapbox content type https://github.com/elastic/elasticsearch-js/pull/1500[#1500] |
| 18 | + |
| 19 | +If you call an API that returns a mapbox conten type, the response body will be a buffer. |
| 20 | + |
| 21 | +[discrete] |
| 22 | +===== Support CA fingerprint validation https://github.com/elastic/elasticsearch-js/pull/1499[#1499] |
| 23 | + |
| 24 | +You can configure the client to only trust certificates that are signed by a specific CA certificate ( CA certificate pinning ) by providing a `caFingerprint` option. This will verify that the fingerprint of the CA certificate that has signed the certificate of the server matches the supplied value. |
| 25 | +a `caFingerprint` option, which will verify the supplied certificate authority fingerprint. |
| 26 | +You must configure a SHA256 digest. |
| 27 | + |
| 28 | +[source,js] |
| 29 | +---- |
| 30 | +const { Client } = require('@elastic/elasticsearch') |
| 31 | +const client = new Client({ |
| 32 | + node: 'https://example.com' |
| 33 | + auth: { ... }, |
| 34 | + // the fingerprint (SHA256) of the CA certificate that is used to sign the certificate that the Elasticsearch node presents for TLS. |
| 35 | + caFingerprint: '20:0D:CA:FA:76:...', |
| 36 | + ssl: { |
| 37 | + // might be required if it's a self-signed certificate |
| 38 | + rejectUnauthorized: false |
| 39 | + } |
| 40 | +}) |
| 41 | +---- |
| 42 | + |
| 43 | +[discrete] |
| 44 | +===== Show the body as string if the response error can't be read as ES error https://github.com/elastic/elasticsearch-js/pull/1509[#1509] |
| 45 | + |
| 46 | +Useful if the errored response does not come from Elasticsearch, but a proxy in the middle for example. |
| 47 | + |
| 48 | +[discrete] |
| 49 | +===== Always display request params and options in request event https://github.com/elastic/elasticsearch-js/pull/1531[#1531] |
| 50 | + |
| 51 | +In some edge cases the params and options weren't available in observabilty events, now they are always defined. |
| 52 | + |
| 53 | +[discrete] |
| 54 | +===== Always emit request aborted event https://github.com/elastic/elasticsearch-js/pull/1534[#1534] |
| 55 | + |
| 56 | +If the client is busy running an async operation, the `.abort()` call might be executed before sending the actual request. In such case, the error was swallowed, now it will always be emitted, either in the `request` or `response` event. |
| 57 | + |
4 | 58 | [discrete]
|
5 | 59 | === 7.14.0
|
6 | 60 |
|
|
0 commit comments