Remove support for proxyConfig and proxyFilter settings in Console in 8.0 #39494
Labels
Breaking Change
Feature:Console
Dev Tools Console Feature
Feature:Dev Tools
required-for-8.0
This work is required to be done before 8.0 lands, bc it relates to a breaking change or similar.
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Background
The
console.proxyFilter
andconsole.proxyConfig
settings were introduced in the original version of Console, which was originally a standalone app called Sense. These settings were originally used to secure the Console requests that would be sent to ES through the Kibana server acting as a proxy, including SSL configuration. Learn more about these settings by reading the 5.0 docs.In 5.3 we deprecated these settings (#9823) in favor of the standard
server.ssl.*
andelasticsearch.ssl.keyPassphrase
settings. See that PR for more info.Related PRs:
Motivation for removal
These settings have been deprecated for a long time and require a lot of code to support. Removing support for them will let us delete a significant amount legacy code.
NOTE: This is a breaking change, so requires a release note with details on how to migrate to the replacement settings as well as a registered Kibana deprecation (#109872).
The text was updated successfully, but these errors were encountered: