ZeroDownTime
/
fluentd-concenter
3
0
Fork 0
Code Issues 1 Pull Requests 1 Packages Projects Releases Wiki Activity

chore(deps): update all non-major dependencies #1

Merged
stefan merged 1 commits from renovate/all-minor-patch into main 2024-04-25 15:08:19 +00:00
Conversation 0 Commits 1 Files Changed 2 +8 -8
renovate commented 2023-12-11 19:06:35 +00:00
Member
Copy Link

This PR contains the following updates:

Package Type Update Change
alpine final minor 3.18 -> 3.19
elasticsearch (source, changelog) minor '>= 7', '< 7.14' -> '>= 7', '< 7.17.11'
fluent-plugin-elasticsearch (changelog) minor "~> 5.2.5" -> "~> 5.4.0"
fluent-plugin-kubernetes_metadata_filter minor "~> 3.2.0" -> "~> 3.4.0"
fluent-plugin-multi-format-parser minor "~> 1.0.0" -> "~> 1.1.0"
fluent-plugin-record-modifier minor "~> 2.1.0" -> "~> 2.2.0"
fluentd patch "1.16.3" -> "1.16.5"
oj (source, changelog) minor "~> 3.15.0" -> "~> 3.16.0"

Release Notes

elastic/elasticsearch-ruby (elasticsearch)

v7.17.10

Compare Source

Backports support for Faraday 2 from elastic-transport. ¡Gracias santiagorodriguez96!

This version of the gem now supports Faraday v2. If you don't have a locked version of Faraday in your project, when you upgrade your gems, Faraday v2 will be installed. 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.

v7.17.9

Compare Source

  • Backports fix from elastic-transport: #​66 - Manticore transport unable to send custom headers with perform_request Pull Request.

v7.17.8

Compare Source

  • Patch releases back to being detached from Elastic stack releases.
  • Tested compatibility with Elasticsearch v7.17 APIs.
  • Tested versions of Ruby for 7.17.8: Ruby (MRI) 2.7, 3.0, 3.1, 3.2, JRuby 9.3, JRuby 9.4.
  • Bugfix in elasticsearch-transport: Fixes enforcing UTF-8 in Response body, causing an error when the string is frozen, particularly when using webmock: issue #​63.

v7.17.7: 7.17.7

Compare Source

  • Compatibility with Elasticsearch v7.17.7 APIs.
  • Tested versions of Ruby for 7.17.7: Ruby (MRI) 2.6, 2.7, 3.0 and 3.1, JRuby 9.3.

v7.17.1: 7.17.1

Compare Source

  • Improves handling of YAML parsing, uses safe_load instead of load when doing the product verification (should only affect Ruby < 3.0).
  • Updates headers setup when using the Manticore adapter. This fixes an issue where the user-agent header was being foverridden even when it was being set on initialization via the transport options. Pull Request, issue.

v7.17.0: 7.17.0

Compare Source

  • Drops Ruby 2.5 from the test matrix. Support for Ruby 2.5 was dropped March 2021.
  • Updates the product verification when the response is a 413 error.

v7.16.3: 7.16.3

Compare Source

API

Bugfix for #​1475, an issue where if you indexed a document with an id such as an id, it would get escaped to an+id instead of an%20id when using index or create. This would result in the document id being an+id instead of the intended value an id.

v7.16.1

Compare Source

Patch release corresponding with Elastic Stack version 7.16.1 that addresses the Apache Log4j2 vulnerability, more information.

Client

The only changes in the client since 7.16.0 are a few minor updates for the Compatibility mode with 8.0. We added the compatibility header in 7.13.0, but now we have integration tests and compatibility tests for version 7.x of the client with Elasticsearch 8.0.

v7.16.0: 7.16.0

Compare Source

7.16.0

Client
  • Adds the delay_on_retry parameter, a value in milliseconds to wait between each failed connection, thanks DinoPullerUqido! Pull Request and backport.
  • Adds CA fingerprinting. You can configure the client to only trust certificates that are signed by a specific CA certificate (CA certificate pinning) by providing a ca_fingerprint option. This will verify that the fingerprint of the CA certificate that has signed the certificate of the server matches the supplied value:
ca_fingerprint = '64F2593F...'
client = Elasticsearch::Client.new(
  host: 'https://elastic:changeme@localhost:9200',
  transport_options: { ssl: { verify: false } },
  ca_fingerprint: ca_fingerprint
)

The verification will be run once per connection.

  • Fixes compression. When compression is set to true, the client will now gzip the request body properly and use the appropiate headers. Thanks johnnyshields! Pull Request and backport.
API
Updates
  • Cleaned up some deprecated code.
  • count - The API is documented as using GET, but it supports both GET and POST on the Elasticsearch side. So it was updated to only use POST when there's a body present, or else use GET. Elasticsearch would still accept a body with GET, but to be more semantically correct in the clients we use POST when there's a body.
  • delete_index_template was updated to support the ignore_404 parameter to ignore 404 errors when attempting to delete a non-existing template.
  • ingest.put_pipeline adds new parameter if_version: Required version for optimistic concurrency control for pipeline updates.
  • ml.put_trained_model: adds new parameter defer_definition_decompression: If set to true and a compressed_definition is provided, the request defers definition decompression and skips relevant validations.
  • nodes.hot_threads adds new parameter sort: The sort order for 'cpu' type (default: total) (options: cpu, total).
  • open_point_in_time: keep_alive is now a required parameter.
  • search_mvt: adds new parameter track_total_hits: Indicate if the number of documents that match the query should be tracked. A number can also be specified, to accurately track the total hit count up to the number.
  • transform.preview_transform: adds new parameter transform_id. Body is now optional and the API will use GET or POST depending on the presence of a body.
APIs promoted from experimental to stable since last version:
  • fleet.global_checkpoints
  • get_script_context
  • get_script_language
  • indices.resolve_index
  • monitoring.bulk
  • rank_eval
  • searchable_snapshots.mount
  • searchable_snapshots.stats
  • security.clear_cached_service_tokens
  • security.create_service_token
  • security.delete_service_token
  • security.get_service_accounts
  • security.get_service_credentials
  • shutdown.delete_node
  • shutdown.get_node
  • shutdown.put_node
  • terms_enum
New APIs
  • fleet.mseach
  • fleet.search
  • indices.modify_data_stream
  • ml.infer_trained_model_deployment
  • ml.start_trained_model_deployment
  • ml.stop_trained_model_deployment
  • migration.get_feature_upgrade_status
  • migration.post_feature_upgrade_status
  • security.enroll_kibana
  • security.enroll_node
  • transform.updgrade_transforms

v7.15.0: 7.15.0

Compare Source

7.15.0

Client
  • Compatibility with Elasticsearch v7.15.0 APIs.
  • We've tested and added documentation on best practices for leveraging the client in a Function-as-a-Service (FaaS) environment to the official docs.
API
  • New experimental endpoints: indices.disk_usage. indices.field_usage_stats, nodes.clear_repositories_metering_archive, get_repositories_metering_info, search_mvt
  • The index parameter is now required for open_point_in_time.
  • The index_metric parameter in nodes.stats adds the shards option.
X-Pack
  • New parameters for ml.put_job: ignore_unavailable, allow_no_indices, ignore_throttled, expand_wildcards.
  • New endpoint: security.query_api_keys.

v7.14.1: 7.14.1

Compare Source

Client

v7.14.0: 7.14.0

Compare Source

Client

Added check that client is connected to an Elasticsearch cluster. If the client isn't connected to a supported Elasticsearch cluster the UnsupportedProductError exception will be raised.

This release changes the way in which the transport layer and the client interact. Previously, when using elasticsearch-transport, Elasticsearch::Transport::Client had a convenient wrapper, so it could be used as Elasticsearch::Client. Now, we are decoupling the transport layer from the Elasticsearch client. If you're using the elasticsearch gem, not much will change. It will instantiate a new Elasticsearch::Transport::Client when you instantiate Elasticsearch::Client and the endpoints from elasticsearch-api will be available.

Elasticsearch::Client has an attr_accessor for the transport instance:

> client = Elasticsearch::Client.new
> client.transport.class
=> Elasticsearch::Transport::Client
> client.transport.transport.class
=> Elasticsearch::Transport::Transport::HTTP::Faraday

The interaction with elasticsearch-api remains unchanged. You can use the API endpoints just like before:

> client.info
=> {"name"=>"instance",
 "cluster_name"=>"elasticsearch",
 "cluster_uuid"=>"id",
 "version"=>
  {"number"=>"7.14.0",
  ...
},
 "tagline"=>"You Know, for Search"}

Or perform request directly from the client which will return an Elasticsearch::Transport::Response object:

> client.perform_request('GET', '/')

### This is the same as doing client.transport.perform_request('GET', '/')
=> #<Elasticsearch::Transport::Transport::Response:0x000055c80bf94bc8
 @&#8203;body=
  {"name"=>"instance",
   "cluster_name"=>"elasticsearch",
   "cluster_uuid"=>"id",
   "version"=>
    {"number"=>"7.14.0-SNAPSHOT",
    ...
    },
   "tagline"=>"You Know, for Search"},
 @&#8203;headers=
  {"content-type"=>"application/json; charset=UTF-8",
   "content-length"=>"571",
   ...
   },
 @&#8203;status=200>

If you have any problems, please report them in this issue.

API

Code is now generated from Elastic artifacts instead of checked out code of Elasticsearch. See the Generator README for more info.

  • Endpoints msearch, msearch_template and search_template remove query_and_fetch and dfs_query_and_fetch options from the search_type parameter.
  • New parameter include_repository in snapshot.get: (boolean) Whether to include the repository name in the snapshot info. Defaults to true.
X-Pack

X-Pack is being deprecated. The first time using xpack on the client, a warning will be triggered. Please check this issue for more information.

  • New endpoints: index_lifecycle_management.migrate_to_data_tiers, machine_learning.reset_job, security.saml_authenticate, security.saml_complete_logout, security.saml_invalidate, security.saml_logout, security.saml_prepare_authentication, security.saml_service_provider_metadata, sql.delete_async, sql.get_async, sql.get_async_status, terms_enum.
  • New experimental endpoints: machine_learning.infer_trained_model_deployment, machine_learning.start_trained_model_deployment, machine_learning.stop_trained_model_deployment.
  • Deprecation: indices.freeze and indices.unfreeze: Frozen indices are deprecated because they provide no benefit given improvements in heap memory utilization. They will be removed in a future release.
uken/fluent-plugin-elasticsearch (fluent-plugin-elasticsearch)

v5.4.3

Compare Source

  • add data_stream_template_use_index_patterns_wildcard in elasticsearch_data_stream (#​1040)

v5.4.2

Compare Source

  • in_elasticsearch: Avoid to use deprecated endpoint for clear_scroll (#​1039)

v5.4.1

Compare Source

v5.4.0

Compare Source

  • Fix support for host/hosts placeholders for ipv6 addresses (#​1030)
  • Handle newer es library (#​1032)

v5.3.0

Compare Source

  • Unpin faraday from v1, upgrade to v2. (#​1012)
    Note that if you can't migrate other plugins from faraday v1 yet, need to keep
    fluent-plugin-elasticsearch v5.2.5.
fabric8io/fluent-plugin-kubernetes_metadata_filter (fluent-plugin-kubernetes_metadata_filter)

v3.4.0

Compare Source

v3.3.0

Compare Source

repeatedly/fluent-plugin-multi-format-parser (fluent-plugin-multi-format-parser)

v1.1.0

Compare Source

repeatedly/fluent-plugin-record-modifier (fluent-plugin-record-modifier)

v2.2.0

Compare Source

ohler55/oj (oj)

v3.16.3

Compare Source

  • Fixed the gemspec to allow earlier versions of the bigdecimal gem.

v3.16.2

Compare Source

  • Fixed documentation formatting.

  • Added option to the "usual" parser to raise an error on an empty input string.

v3.16.1

Compare Source

v3.16.0

Compare Source

  • Added the float_format option.

  • Expanded the max_nesting option to allow integer values as well as
    the previous boolean (true or nil).

  • Skip nesting tests with Truffle Ruby in the json gem tests.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | alpine | final | minor | `3.18` -> `3.19` | | [elasticsearch](https://www.elastic.co/guide/en/elasticsearch/client/ruby-api/current/index.html) ([source](https://github.com/elastic/elasticsearch-ruby), [changelog](https://github.com/elastic/elasticsearch-ruby/blob/main/CHANGELOG.md)) | | minor | `'>= 7', '< 7.14'` -> `'>= 7', '< 7.17.11'` | | [fluent-plugin-elasticsearch](https://github.com/uken/fluent-plugin-elasticsearch) ([changelog](https://github.com/uken/fluent-plugin-elasticsearch/blob/master/History.md)) | | minor | `"~> 5.2.5"` -> `"~> 5.4.0"` | | [fluent-plugin-kubernetes_metadata_filter](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter) | | minor | `"~> 3.2.0"` -> `"~> 3.4.0"` | | [fluent-plugin-multi-format-parser](https://github.com/repeatedly/fluent-plugin-multi-format-parser) | | minor | `"~> 1.0.0"` -> `"~> 1.1.0"` | | [fluent-plugin-record-modifier](https://github.com/repeatedly/fluent-plugin-record-modifier) | | minor | `"~> 2.1.0"` -> `"~> 2.2.0"` | | fluentd | | patch | `"1.16.3"` -> `"1.16.5"` | | [oj](http://www.ohler.com/oj/) ([source](https://github.com/ohler55/oj), [changelog](https://github.com/ohler55/oj/blob/master/CHANGELOG.md)) | | minor | `"~> 3.15.0"` -> `"~> 3.16.0"` | --- ### Release Notes <details> <summary>elastic/elasticsearch-ruby (elasticsearch)</summary> ### [`v7.17.10`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.17.10) [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.17.9...v7.17.10) Backports support for Faraday 2 from `elastic-transport`. ¡Gracias [santiagorodriguez96](https://github.com/santiagorodriguez96)! This version of the gem now supports Faraday v2. If you don't have a locked version of Faraday in your project, when you upgrade your gems, Faraday v2 will be installed. 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: ```ruby ### 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](https://github.com/elastic/elasticsearch-ruby/issues) if you encounter any problems. ### [`v7.17.9`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.17.9) [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.17.8...v7.17.9) - Backports fix from `elastic-transport`: [#&#8203;66](https://github.com/elastic/elastic-transport-ruby/issues/66) - Manticore transport unable to send custom headers with `perform_request` [Pull Request](https://github.com/elastic/elastic-transport-ruby/pull/69). ### [`v7.17.8`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.17.8) [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.17.7...v7.17.8) - Patch releases back to being detached from Elastic stack releases. - Tested compatibility with Elasticsearch v7.17 APIs. - Tested versions of Ruby for 7.17.8: Ruby (MRI) 2.7, 3.0, 3.1, 3.2, JRuby 9.3, JRuby 9.4. - Bugfix in elasticsearch-transport: Fixes enforcing UTF-8 in Response body, causing an error when the string is frozen, particularly when using webmock: [issue #&#8203;63](https://github.com/elastic/elastic-transport-ruby/issues/63). ### [`v7.17.7`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.17.7): 7.17.7 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.17.1...v7.17.7) - Compatibility with Elasticsearch v7.17.7 APIs. - Tested versions of Ruby for 7.17.7: Ruby (MRI) 2.6, 2.7, 3.0 and 3.1, JRuby 9.3. ### [`v7.17.1`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.17.1): 7.17.1 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.17.0...v7.17.1) - Improves handling of YAML parsing, uses `safe_load` instead of `load` when doing the product verification (should only affect Ruby < 3.0). - Updates headers setup when using the Manticore adapter. This fixes an issue where the user-agent header was being foverridden even when it was being set on initialization via the transport options. [Pull Request](https://github.com/elastic/elasticsearch-ruby/pull/1685), [issue](https://github.com/elastic/elasticsearch-ruby/issues/1684). ### [`v7.17.0`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.17.0): 7.17.0 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.16.3...v7.17.0) - Drops Ruby 2.5 from the test matrix. Support for Ruby 2.5 was dropped March 2021. - Updates the product verification when the response is a `413` error. ### [`v7.16.3`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.16.3): 7.16.3 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.16.1...v7.16.3) ##### API Bugfix for [#&#8203;1475](https://github.com/elastic/elasticsearch-ruby/issues/1475), an issue where if you indexed a document with an id such as `an id`, it would get escaped to `an+id` instead of `an%20id` when using `index` or `create`. This would result in the document id being `an+id` instead of the intended value `an id`. ### [`v7.16.1`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.16.1) [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.16.0...v7.16.1) Patch release corresponding with Elastic Stack version 7.16.1 that addresses the Apache Log4j2 vulnerability, [more information](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476). ##### Client The only changes in the client since 7.16.0 are a few minor updates for the [Compatibility mode with 8.0](https://www.elastic.co/guide/en/elasticsearch/client/ruby-api/current/connecting.html#client-comp). We added the compatibility header in `7.13.0`, but now we have integration tests and compatibility tests for version `7.x` of the client with Elasticsearch `8.0`. ### [`v7.16.0`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.16.0): 7.16.0 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.15.0...v7.16.0) #### 7.16.0 ##### Client - Adds the `delay_on_retry` parameter, a value in milliseconds to wait between each failed connection, thanks [DinoPullerUqido](https://github.com/DinoPullerUqido)! [Pull Request](https://github.com/elastic/elasticsearch-ruby/pull/1521) and [backport](https://github.com/elastic/elasticsearch-ruby/pull/1523). - Adds *CA fingerprinting*. You can configure the client to only trust certificates that are signed by a specific CA certificate (CA certificate pinning) by providing a `ca_fingerprint` option. This will verify that the fingerprint of the CA certificate that has signed the certificate of the server matches the supplied value: ```ruby ca_fingerprint = '64F2593F...' client = Elasticsearch::Client.new( host: 'https://elastic:changeme@localhost:9200', transport_options: { ssl: { verify: false } }, ca_fingerprint: ca_fingerprint ) ``` The verification will be run once per connection. - Fixes compression. When `compression` is set to `true`, the client will now gzip the request body properly and use the appropiate headers. Thanks [johnnyshields](https://github.com/johnnyshields)! [Pull Request](https://github.com/elastic/elasticsearch-ruby/pull/1478) and [backport](https://github.com/elastic/elasticsearch-ruby/pull/1526). ##### API ##### Updates - Cleaned up some deprecated code. - `count` - The API is documented as using `GET`, but it supports both GET and POST on the Elasticsearch side. So it was updated to only use `POST` when there's a body present, or else use `GET`. Elasticsearch would still accept a body with `GET`, but to be more semantically correct in the clients we use `POST` when there's a body. - `delete_index_template` was updated to support the `ignore_404` parameter to ignore 404 errors when attempting to delete a non-existing template. - `ingest.put_pipeline` adds new parameter `if_version`: Required version for optimistic concurrency control for pipeline updates. - `ml.put_trained_model`: adds new parameter `defer_definition_decompression`: If set to `true` and a `compressed_definition` is provided, the request defers definition decompression and skips relevant validations. - `nodes.hot_threads` adds new parameter `sort`: The sort order for 'cpu' type (default: total) (options: cpu, total). - `open_point_in_time`: `keep_alive` is now a required parameter. - `search_mvt`: adds new parameter `track_total_hits`: Indicate if the number of documents that match the query should be tracked. A number can also be specified, to accurately track the total hit count up to the number. - `transform.preview_transform`: adds new parameter `transform_id`. Body is now optional and the API will use `GET` or `POST` depending on the presence of a body. ##### APIs promoted from experimental to stable since last version: - `fleet.global_checkpoints` - `get_script_context` - `get_script_language` - `indices.resolve_index` - `monitoring.bulk` - `rank_eval` - `searchable_snapshots.mount` - `searchable_snapshots.stats` - `security.clear_cached_service_tokens` - `security.create_service_token` - `security.delete_service_token` - `security.get_service_accounts` - `security.get_service_credentials` - `shutdown.delete_node` - `shutdown.get_node` - `shutdown.put_node` - `terms_enum` ##### New APIs - `fleet.mseach` - `fleet.search` - `indices.modify_data_stream` - `ml.infer_trained_model_deployment` - `ml.start_trained_model_deployment` - `ml.stop_trained_model_deployment` - `migration.get_feature_upgrade_status` - `migration.post_feature_upgrade_status` - `security.enroll_kibana` - `security.enroll_node` - `transform.updgrade_transforms` ### [`v7.15.0`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.15.0): 7.15.0 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.14.1...v7.15.0) #### 7.15.0 ##### Client - Compatibility with Elasticsearch v7.15.0 APIs. - We've tested and added documentation on best practices for leveraging the client in a Function-as-a-Service (FaaS) environment to the [official docs](https://www.elastic.co/guide/en/elasticsearch/client/ruby-api/current/connecting.html#client-faas). ##### API - New experimental endpoints: `indices.disk_usage`. `indices.field_usage_stats`, `nodes.clear_repositories_metering_archive`, `get_repositories_metering_info`, [`search_mvt`](https://www.elastic.co/guide/en/elasticsearch/reference/master/search-vector-tile-api.html) - The `index` parameter is now required for `open_point_in_time`. - The `index_metric` parameter in `nodes.stats` adds the `shards` option. ##### X-Pack - New parameters for `ml.put_job`: `ignore_unavailable`, `allow_no_indices`, `ignore_throttled`, `expand_wildcards`. - New endpoint: [`security.query_api_keys`](https://www.elastic.co/guide/en/elasticsearch/reference/7.15/security-api-query-api-key.html). ### [`v7.14.1`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.14.1): 7.14.1 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.14.0...v7.14.1) ##### Client - Fixes for Manticore Implementation: Addresses custom headers on initialization (https://github.com/elastic/elasticsearch-ruby/commit/3732dd4f6de75365460fa99c1cd89668b107ef1c) and fixes tracing (https://github.com/elastic/elasticsearch-ruby/commit/3c48ebd9a783988d1f71bfb9940459832ccd63e4). Related to [#&#8203;1426](https://github.com/elastic/elasticsearch-ruby/issues/1426) and [#&#8203;1428](https://github.com/elastic/elasticsearch-ruby/issues/1428). ### [`v7.14.0`](https://github.com/elastic/elasticsearch-ruby/releases/tag/v7.14.0): 7.14.0 [Compare Source](https://github.com/elastic/elasticsearch-ruby/compare/v7.14.0.pre...v7.14.0) ##### Client Added check that client is connected to an Elasticsearch cluster. If the client isn't connected to a supported Elasticsearch cluster the `UnsupportedProductError` exception will be raised. This release changes the way in which the transport layer and the client interact. Previously, when using `elasticsearch-transport`, `Elasticsearch::Transport::Client` had a convenient wrapper, so it could be used as `Elasticsearch::Client`. Now, we are decoupling the transport layer from the Elasticsearch client. If you're using the `elasticsearch` gem, not much will change. It will instantiate a new `Elasticsearch::Transport::Client` when you instantiate `Elasticsearch::Client` and the endpoints from `elasticsearch-api` will be available. `Elasticsearch::Client` has an `attr_accessor` for the transport instance: ```ruby > client = Elasticsearch::Client.new > client.transport.class => Elasticsearch::Transport::Client > client.transport.transport.class => Elasticsearch::Transport::Transport::HTTP::Faraday ``` The interaction with `elasticsearch-api` remains unchanged. You can use the API endpoints just like before: ```ruby > client.info => {"name"=>"instance", "cluster_name"=>"elasticsearch", "cluster_uuid"=>"id", "version"=> {"number"=>"7.14.0", ... }, "tagline"=>"You Know, for Search"} ``` Or perform request directly from the client which will return an `Elasticsearch::Transport::Response` object: ```ruby > client.perform_request('GET', '/') ### This is the same as doing client.transport.perform_request('GET', '/') => #<Elasticsearch::Transport::Transport::Response:0x000055c80bf94bc8 @&#8203;body= {"name"=>"instance", "cluster_name"=>"elasticsearch", "cluster_uuid"=>"id", "version"=> {"number"=>"7.14.0-SNAPSHOT", ... }, "tagline"=>"You Know, for Search"}, @&#8203;headers= {"content-type"=>"application/json; charset=UTF-8", "content-length"=>"571", ... }, @&#8203;status=200> ``` If you have any problems, please report them in [this issue](https://github.com/elastic/elasticsearch-ruby/issues/1344). ##### API Code is now generated from Elastic artifacts instead of checked out code of Elasticsearch. See [the Generator README](https://github.com/elastic/elasticsearch-ruby/blob/7.14/elasticsearch-api/utils/README.md#generate) for more info. - Endpoints `msearch`, `msearch_template` and `search_template` remove `query_and_fetch` and `dfs_query_and_fetch` options from the `search_type` parameter. - New parameter `include_repository` in `snapshot.get`: (boolean) Whether to include the repository name in the snapshot info. Defaults to true. ##### X-Pack X-Pack is being deprecated. The first time using `xpack` on the client, a warning will be triggered. Please check [this issue](https://github.com/elastic/elasticsearch-ruby/issues/1274) for more information. - New endpoints: `index_lifecycle_management.migrate_to_data_tiers`, `machine_learning.reset_job`, `security.saml_authenticate`, `security.saml_complete_logout`, `security.saml_invalidate`, `security.saml_logout`, `security.saml_prepare_authentication`, `security.saml_service_provider_metadata`, `sql.delete_async`, `sql.get_async`, `sql.get_async_status`, `terms_enum`. - New experimental endpoints: `machine_learning.infer_trained_model_deployment`, `machine_learning.start_trained_model_deployment`, `machine_learning.stop_trained_model_deployment`. - Deprecation: `indices.freeze` and `indices.unfreeze`: Frozen indices are deprecated because they provide no benefit given improvements in heap memory utilization. They will be removed in a future release. </details> <details> <summary>uken/fluent-plugin-elasticsearch (fluent-plugin-elasticsearch)</summary> ### [`v5.4.3`](https://github.com/uken/fluent-plugin-elasticsearch/blob/HEAD/History.md#543) [Compare Source](https://github.com/uken/fluent-plugin-elasticsearch/compare/v5.4.2...v5.4.3) - add data_stream_template_use_index_patterns_wildcard in elasticsearch_data_stream ([#&#8203;1040](https://github.com/uken/fluent-plugin-elasticsearch/issues/1040)) ### [`v5.4.2`](https://github.com/uken/fluent-plugin-elasticsearch/blob/HEAD/History.md#542) [Compare Source](https://github.com/uken/fluent-plugin-elasticsearch/compare/v5.4.1...v5.4.2) - in_elasticsearch: Avoid to use deprecated endpoint for clear_scroll ([#&#8203;1039](https://github.com/uken/fluent-plugin-elasticsearch/issues/1039)) ### [`v5.4.1`](https://github.com/uken/fluent-plugin-elasticsearch/blob/HEAD/History.md#541) [Compare Source](https://github.com/uken/fluent-plugin-elasticsearch/compare/v5.4.0...v5.4.1) - Adjust ilm endpoint ([#&#8203;1036](https://github.com/uken/fluent-plugin-elasticsearch/issues/1036)) ### [`v5.4.0`](https://github.com/uken/fluent-plugin-elasticsearch/blob/HEAD/History.md#540) [Compare Source](https://github.com/uken/fluent-plugin-elasticsearch/compare/v5.3.0...v5.4.0) - Fix support for host/hosts placeholders for ipv6 addresses ([#&#8203;1030](https://github.com/uken/fluent-plugin-elasticsearch/issues/1030)) - Handle newer es library ([#&#8203;1032](https://github.com/uken/fluent-plugin-elasticsearch/issues/1032)) ### [`v5.3.0`](https://github.com/uken/fluent-plugin-elasticsearch/blob/HEAD/History.md#530) [Compare Source](https://github.com/uken/fluent-plugin-elasticsearch/compare/v5.2.5...v5.3.0) - Unpin `faraday` from v1, upgrade to v2. ([#&#8203;1012](https://github.com/uken/fluent-plugin-elasticsearch/issues/1012)) Note that if you can't migrate other plugins from `faraday` v1 yet, need to keep fluent-plugin-elasticsearch v5.2.5. </details> <details> <summary>fabric8io/fluent-plugin-kubernetes_metadata_filter (fluent-plugin-kubernetes_metadata_filter)</summary> ### [`v3.4.0`](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/compare/v3.3.0...v3.4.0) [Compare Source](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/compare/v3.3.0...v3.4.0) ### [`v3.3.0`](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/compare/v3.2.0...v3.3.0) [Compare Source](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/compare/v3.2.0...v3.3.0) </details> <details> <summary>repeatedly/fluent-plugin-multi-format-parser (fluent-plugin-multi-format-parser)</summary> ### [`v1.1.0`](https://github.com/repeatedly/fluent-plugin-multi-format-parser/compare/v1.0.0...v1.1.0) [Compare Source](https://github.com/repeatedly/fluent-plugin-multi-format-parser/compare/v1.0.0...v1.1.0) </details> <details> <summary>repeatedly/fluent-plugin-record-modifier (fluent-plugin-record-modifier)</summary> ### [`v2.2.0`](https://github.com/repeatedly/fluent-plugin-record-modifier/compare/v2.1.1...v2.2.0) [Compare Source](https://github.com/repeatedly/fluent-plugin-record-modifier/compare/v2.1.1...v2.2.0) </details> <details> <summary>ohler55/oj (oj)</summary> ### [`v3.16.3`](https://github.com/ohler55/oj/blob/HEAD/CHANGELOG.md#3163---2023-12-11) [Compare Source](https://github.com/ohler55/oj/compare/v3.16.2...v3.16.3) - Fixed the gemspec to allow earlier versions of the bigdecimal gem. ### [`v3.16.2`](https://github.com/ohler55/oj/blob/HEAD/CHANGELOG.md#3162---2023-12-06) [Compare Source](https://github.com/ohler55/oj/compare/v3.16.1...v3.16.2) - Fixed documentation formatting. - Added option to the "usual" parser to raise an error on an empty input string. ### [`v3.16.1`](https://github.com/ohler55/oj/blob/HEAD/CHANGELOG.md#3161---2023-09-01) [Compare Source](https://github.com/ohler55/oj/compare/v3.16.0...v3.16.1) - Fixed exception type on number parsing. (thank you [@&#8203;jasonpenny](https://github.com/jasonpenny)) ### [`v3.16.0`](https://github.com/ohler55/oj/blob/HEAD/CHANGELOG.md#3160---2023-08-16) [Compare Source](https://github.com/ohler55/oj/compare/v3.15.1...v3.16.0) - Added the `float_format` option. - Expanded the `max_nesting` option to allow integer values as well as the previous boolean (true or nil). - Skip nesting tests with Truffle Ruby in the json gem tests. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy42OC40IiwidXBkYXRlZEluVmVyIjoiMzcuMjY3LjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIn0=-->
renovate added the
renovate
 label 2023-12-11 19:06:35 +00:00
renovate force-pushed renovate/all-minor-patch from 9d69bfd807 to b4fc6d9764 2023-12-13 19:48:44 +00:00 Compare
renovate force-pushed renovate/all-minor-patch from b4fc6d9764 to a342dc2e4a 2024-03-15 03:15:43 +00:00 Compare
renovate force-pushed renovate/all-minor-patch from a342dc2e4a to 7bda02d63f 2024-03-28 03:02:51 +00:00 Compare
stefan merged commit c87649cc61 into main 2024-04-25 15:08:19 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
renovate

Dependency via Renovate

No Label
renovate
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ZeroDownTime/fluentd-concenter#1
No description provided.
Delete Branch "renovate/all-minor-patch"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?