Bump elasticsearch from 7.8.0 to 8.5.2

[dependabot]

Bumps elasticsearch from 7.8.0 to 8.5.2.

Release notes

Sourced from elasticsearch's releases.

8.5.2

API Bugfix

Fixes security.create_service_token API, uses POST when token name isn't present. Thanks @​carlosdelest for reporting in #1961.

8.5.1

Bugfix

Fixes bug when instantiating client with api_key: When passing in api_key and transport_options that don't include headers to the client, the api_key code would overwrite the arguments passed in for transport_options. This was fixed in this Pull Request. Thanks svdasein for reporting in #1940.

8.5.0

• Tested versions of Ruby for 8.5.0: Ruby (MRI) 2.7, 3.0 and 3.1, JRuby 9.3.

Client

With the latest release of elastic-transport - v8.1.0 - this gem now supports Faraday v2. Elasticsearch Ruby has an open dependency on elastic-transport ('elastic-transport', '~> 8'), so when you upgrade your gems, 8.1.0 will be installed. This supports both Faraday v1 and Faraday v2. The main change on dependencies when using Faraday v2 is all adapters, except for the default net_http one, have been moved out of Faraday into separate gems. This means if you're not using the default adapter and you migrate to Faraday v2, you'll need to add the adapter gems to your Gemfile.

These are the gems required for the different adapters with Faraday 2, instead of the libraries on which they were based:

# HTTPCLient
gem 'faraday-httpclient'
# NetHTTPPersistent
gem 'faraday-net_http_persistent'
# Patron
gem 'faraday-patron'
# Typhoeus
gem 'faraday-typhoeus'

Things should work fine if you migrate to Faraday 2 as long as you include the adapter (unless you're using the default one net-http), but worst case scenario, you can always lock the version of Faraday in your project to 1.x: gem 'faraday', '~> 1'

Be aware if migrating to Faraday v2 that it requires at least Ruby 2.6, unlike Faraday v1 which requires 2.4.

Troubleshooting

If you see a message like: :adapter is not registered on Faraday::Adapter (Faraday::Error) Then you probably need to include the adapter library in your gemfile and require it.

Please submit an issue if you encounter any problems.

API

New APIs

• machine_learning.clear_trained_model_deployment_cache - Clear the cached results from a trained model deployment (Beta).
• security.bulk_update_api_keys - Updates the attributes of multiple existing API keys.

... (truncated)

Changelog

Sourced from elasticsearch's changelog.

8.5.2 Release notes

API Bugfix

Fixes security.create_service_token API, uses POST when token name isn't present. Thanks @​carlosdelest for reporting in #1961.

8.5.1 Release notes

Bugfix

Fixes bug when instantiating client with api_key: When passing in api_key and transport_options that don't include headers to the client, the api_key code would overwrite the arguments passed in for transport_options. This was fixed in this Pull Request. Thanks svdasein for reporting in #1940.

8.5.0 Release notes

• Tested versions of Ruby for 8.5.0: Ruby (MRI) 2.7, 3.0 and 3.1, JRuby 9.3.

Client

With the latest release of elastic-transport - v8.1.0 - this gem now supports Faraday v2. Elasticsearch Ruby has an open dependency on elastic-transport ('elastic-transport', '~> 8'), so when you upgrade your gems, 8.1.0 will be installed. This supports both Faraday v1 and Faraday v2. The main change on dependencies when using Faraday v2 is all adapters, except for the default net_http one, have been moved out of Faraday into separate gems. This means if you're not using the default adapter and you migrate to Faraday v2, you'll need to add the adapter gems to your Gemfile.

These are the gems required for the different adapters with Faraday 2, instead of the libraries on which they were based:

# HTTPCLient
gem 'faraday-httpclient'
NetHTTPPersistent
gem 'faraday-net_http_persistent'
Patron
gem 'faraday-patron'
Typhoeus
gem 'faraday-typhoeus'

Things should work fine if you migrate to Faraday 2 as long as you include the adapter (unless you're using the default one net-http), but worst case scenario, you can always lock the version of Faraday in your project to 1.x: gem 'faraday', '~> 1'

Be aware if migrating to Faraday v2 that it requires at least Ruby 2.6, unlike Faraday v1 which requires 2.4.

Troubleshooting

If you see a message like: :adapter is not registered on Faraday::Adapter (Faraday::Error) Then you probably need to include the adapter library in your gemfile and require it.

Please submit an issue if you encounter any problems.

... (truncated)

Commits

• 3f6c1bf [API] Updates create_service_token with generated code
• e89f0d5 Use POST when token name is not present
• 0d0b0bc [API] Generator: Use POST for create_service_token when name not present
• c398d9a [DOCS] 8.5.1 Release notes
• 9c0003d Bumps 8.5 to 8.5.2
• ebd5c6b [DOCS] Updates connecting with API Key
• 5d60b59 Bumps 8.5 to 8.5.1
• b3d8364 [DOCS] Adds Release Notes for 8.5.0
• 8ec8f8e [Test Runner] Adds suport for split_key, from user_profile tests
• 232051b [Test Runner] Support split_key when running user profile actions from test
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)