From a6c9a5e891bd7e3de6e56e19a29fff2f4b48bff1 Mon Sep 17 00:00:00 2001 From: Tim Vernum Date: Mon, 7 Feb 2022 11:34:51 +1100 Subject: [PATCH 1/2] Document removal of custom REST wrappers in 8.0 In #71061 we removed support for custom REST Handler Wrappers. This change adds that information to the migration guide under the "Plugin changes" section --- .../migrate_8_0/plugin-changes.asciidoc | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc b/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc index f4ac2bcf6a9ab..0a8852f061032 100644 --- a/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc +++ b/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc @@ -45,4 +45,26 @@ If you run {es} using Docker and you are managing plugins using a they already installed. If any of these plugins are specified in your configuration file, {es} will ignore them and emit a warning log message. ==== + +.Third party plugins can no longer intercept REST requests (RestHandlerWrapper) +[%collapsible] +==== +*Details* + +In previous versions of {es}, plugins were able to implement the +`getRestHandlerWrapper` method which would allow the plugin to intercept all +REST requests to the node. One of the common uses of this feature was to +implement custom security plugins that replaced the built-in +{security-features}. This extension point is no longer available to +third-party plugins. + +*Impact* + +Some third party plugins that existed for earlier versions of {es} may not be +compatible with {es} version 8.0 or higher. + +If you depend on any third-party plugins (that is, plugins that are not +produced and supported by Elastic) then you should check with the plugin author +and ensure that the plugin is available for your target version of {es} before +you upgrade. +==== + //end::notable-breaking-changes[] From 47e2fad2793847ebb0d0d4cc1a5016d9811fa458 Mon Sep 17 00:00:00 2001 From: Tim Vernum Date: Tue, 8 Feb 2022 11:35:01 +1100 Subject: [PATCH 2/2] Apply suggested changes from @lockwritesdocs Co-authored-by: Adam Locke --- .../migrate_8_0/plugin-changes.asciidoc | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc b/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc index 0a8852f061032..4955cfc189504 100644 --- a/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc +++ b/docs/reference/migration/migrate_8_0/plugin-changes.asciidoc @@ -46,25 +46,25 @@ they already installed. If any of these plugins are specified in your configuration file, {es} will ignore them and emit a warning log message. ==== -.Third party plugins can no longer intercept REST requests (RestHandlerWrapper) +.Third party plugins can no longer intercept REST requests (`RestHandlerWrapper`) [%collapsible] ==== *Details* + -In previous versions of {es}, plugins were able to implement the -`getRestHandlerWrapper` method which would allow the plugin to intercept all -REST requests to the node. One of the common uses of this feature was to -implement custom security plugins that replaced the built-in -{security-features}. This extension point is no longer available to -third-party plugins. +In previous versions of {es}, third-party plugins could implement the +`getRestHandlerWrapper` method to intercept all REST requests to the node. A +common use of this feature was to implement custom security plugins to replace +the built-in {security-features}. This extension point is no longer available +to third-party plugins. + *Impact* + -Some third party plugins that existed for earlier versions of {es} may not be -compatible with {es} version 8.0 or higher. +Some third-party plugins that were designed to work with earlier versions of +{es} might not be compatible with {es} version 8.0 or later. + +If you depend on any plugins that are not produced and supported by Elastic, +check with the plugin author and ensure that the plugin is available for your +target version of {es} before upgrading. -If you depend on any third-party plugins (that is, plugins that are not -produced and supported by Elastic) then you should check with the plugin author -and ensure that the plugin is available for your target version of {es} before -you upgrade. ==== //end::notable-breaking-changes[]