Skip to content
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.

Sign up for GitHub

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

Document removal of custom REST wrappers in 8.0 #83565

Merged
merged 2 commits into from
Feb 8, 2022
Merged

Document removal of custom REST wrappers in 8.0 #83565

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a6c9a5e
Document removal of custom REST wrappers in 8.0
tvernum Feb 7, 2022
47e2fad
Apply suggested changes from @lockwritesdocs
tvernum Feb 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/reference/migration/migrate_8_0/plugin-changes.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}, 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 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.

====

//end::notable-breaking-changes[]