Merge branch 'master' of github.com:elastic/kibana into generate-erro…

…rs-metrics

docs/dev-tools/console/console.asciidoc

@@ -129,13 +129,3 @@ image::dev-tools/console/images/console-settings.png["Console Settings", width=6
 
 For a list of available keyboard
 shortcuts, click *Help*.
-
-[float]
-[[console-settings]]
-=== Disable Console
-
-deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-If you don’t want to use *Console*, you can disable it by setting `console.enabled`
-to `false` in your `kibana.yml` configuration file. Changing this setting
-causes the server to regenerate assets on the next startup,
-which might cause a delay before pages start being served.

docs/migration/migrate_8_0.asciidoc

@@ -17,6 +17,7 @@ See also <<whats-new>> and <<release-notes>>.
 //NOTE: The notable-breaking-changes tagged regions are re-used in the
 //Installation and Upgrade Guide
 
+// tag::notable-breaking-changes[]
 [float]
 [[breaking_80_index_pattern_changes]]
 === Index pattern changes
@@ -30,18 +31,24 @@ to function as expected. Support for these index patterns has been removed in 8.
 *Impact:* You must migrate your time_based index patterns to a wildcard pattern,
 for example, `logstash-*`.
 
-
 [float]
 [[breaking_80_setting_changes]]
 === Settings changes
 
-// tag::notable-breaking-changes[]
 [float]
 ==== Multitenancy by changing `kibana.index` is no longer supported
 *Details:* `kibana.index`, `xpack.reporting.index` and `xpack.task_manager.index` can no longer be specified. 
 
 *Impact:* Users who relied on changing these settings to achieve multitenancy should use *Spaces*, cross-cluster replication, or cross-cluster search instead. To migrate to *Spaces*, users are encouraged to use saved object management to export their saved objects from a tenant into the default tenant in a space. Improvements are planned to improve on this workflow. See https://github.com/elastic/kibana/issues/82020 for more details.   
 
+[float]
+==== Disabling most plugins with the `{plugin_name}.enabled` setting is no longer supported
+*Details:* The ability for most plugins to be disabled using the `{plugin_name}.enabled` config option has been removed.
+
+*Impact:* Some plugins, such as `telemetry`, `newsfeed`, `reporting`, and the various `vis_type` plugins will continue to support this setting, however the rest of the plugins that ship with Kibana will not. By default, any newly created plugins will not support this configuration unless it is explicitly added to the plugin's `configSchema`.
+
+If you are currently using one of these settings in your Kibana config, please remove it before upgrading to 8.0. If you were using these settings to control user access to certain Kibana applications, we recommend leveraging Feature Controls instead.
+
 [float]
 ==== Legacy browsers are now rejected by default
 *Details:* `csp.strict` is now enabled by default, so Kibana will fail to load for older, legacy browsers that do not enforce basic Content Security Policy protections - notably Internet Explorer 11.

docs/settings/apm-settings.asciidoc

@@ -40,10 +40,6 @@ Changing these settings may disable features of the APM App.
 
 [cols="2*<"]
 |===
-| `xpack.apm.enabled` {ess-icon}
-  | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-  Set to `false` to disable the APM app. Defaults to `true`.
-
 | `xpack.apm.maxServiceEnvironments` {ess-icon}
   | Maximum number of unique service environments recognized by the UI. Defaults to `100`.
 

docs/settings/fleet-settings.asciidoc

@@ -20,9 +20,6 @@ See the {fleet-guide}/index.html[{fleet}] docs for more information.
 
 [cols="2*<"]
 |===
-| `xpack.fleet.enabled` {ess-icon}
-  | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-  Set to `true` (default) to enable {fleet}. 
 | `xpack.fleet.agents.enabled` {ess-icon}
   | Set to `true` (default) to enable {fleet}. 
 |===

docs/settings/general-infra-logs-ui-settings.asciidoc

@@ -1,8 +1,4 @@
 
-`xpack.infra.enabled`::
-deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-Set to `false` to disable the Logs and Metrics app plugin {kib}. Defaults to `true`.
-
 `xpack.infra.sources.default.logAlias`::
 Index pattern for matching indices that contain log data. Defaults to `filebeat-*,kibana_sample_data_logs*`. To match multiple wildcard patterns, use a comma to separate the names, with no space after the comma. For example, `logstash-app1-*,default-logs-*`.
 

docs/settings/monitoring-settings.asciidoc

@@ -31,13 +31,6 @@ For more information, see
 
 [cols="2*<"]
 |===
-| `monitoring.enabled`
-  | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-  Set to `true` (default) to enable the {monitor-features} in {kib}. Unlike the
-  <<monitoring-ui-enabled, `monitoring.ui.enabled`>> setting, when this setting is `false`, the
-  monitoring back-end does not run and {kib} stats are not sent to the monitoring
-  cluster.
-
 | `monitoring.ui.ccs.enabled`
   | Set to `true` (default) to enable {ref}/modules-cross-cluster-search.html[cross-cluster search] of your monitoring data. The {ref}/modules-remote-clusters.html#remote-cluster-settings[`remote_cluster_client`] role must exist on each node.
 

docs/settings/settings-xkb.asciidoc

@@ -13,11 +13,8 @@ For more {kib} configuration settings, see <<settings>>.
 include::alert-action-settings.asciidoc[]
 include::apm-settings.asciidoc[]
 include::banners-settings.asciidoc[]
-include::dev-settings.asciidoc[]
-include::graph-settings.asciidoc[]
 include::infrastructure-ui-settings.asciidoc[]
 include::logs-ui-settings.asciidoc[]
-include::ml-settings.asciidoc[]
 include::reporting-settings.asciidoc[]
 include::spaces-settings.asciidoc[]
 include::task-manager-settings.asciidoc[]

docs/settings/url-drilldown-settings.asciidoc

@@ -8,10 +8,6 @@ Configure the URL drilldown settings in your `kibana.yml` configuration file.
 
 [cols="2*<"]
 |===
-| [[url-drilldown-enabled]] `url_drilldown.enabled`
- | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
- When `true`, enables URL drilldowns on your {kib} instance.
-
 | [[external-URL-policy]] `externalUrl.policy`
  | Configures the external URL policies. URL drilldowns respect the global *External URL* service, which you can use to deny or allow external URLs.
 By default all external URLs are allowed.

docs/setup/settings.asciidoc

@@ -20,11 +20,12 @@ configuration using `${MY_ENV_VAR}` syntax.
 [cols="2*<"]
 |===
 
-| `console.enabled:`
- | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-Toggling this causes the server to regenerate assets on the next startup,
-which may cause a delay before pages start being served.
-Set to `false` to disable Console. *Default: `true`*
+| `csp.rules:`
+ | deprecated:[7.14.0,"In 8.0 and later, this setting will no longer be supported."]
+A https://w3c.github.io/webappsec-csp/[Content Security Policy] template
+that disables certain unnecessary and potentially insecure capabilities in
+the browser. It is strongly recommended that you keep the default CSP rules
+that ship with {kib}.
 
 | `csp.script_src:`
 | Add sources for the https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src[Content Security Policy `script-src` directive].
@@ -688,15 +689,6 @@ sources and images. When false, Vega can only get data from {es}. *Default: `fal
 `exploreDataInChart.enabled`
  | Enables you to view the underlying documents in a data series from a dashboard panel. *Default: `false`*
 
-| `xpack.license_management.enabled`
- | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-Set this value to false to disable the License Management UI.
-*Default: `true`*
-
-| `xpack.rollup.enabled:`
- | deprecated:[7.16.0,"In 8.0 and later, this setting will no longer be supported."]
-Set this value to false to disable the Rollup UI. *Default: true*
-
 | `i18n.locale` {ess-icon}
  | Set this value to change the {kib} interface language.
 Valid locales are: `en`, `zh-CN`, `ja-JP`. *Default: `en`*
@@ -706,14 +698,11 @@ Valid locales are: `en`, `zh-CN`, `ja-JP`. *Default: `en`*
 include::{kib-repo-dir}/settings/alert-action-settings.asciidoc[]
 include::{kib-repo-dir}/settings/apm-settings.asciidoc[]
 include::{kib-repo-dir}/settings/banners-settings.asciidoc[]
-include::{kib-repo-dir}/settings/dev-settings.asciidoc[]
-include::{kib-repo-dir}/settings/graph-settings.asciidoc[]
 include::{kib-repo-dir}/settings/fleet-settings.asciidoc[]
 include::{kib-repo-dir}/settings/i18n-settings.asciidoc[]
 include::{kib-repo-dir}/settings/logging-settings.asciidoc[]
 include::{kib-repo-dir}/settings/logs-ui-settings.asciidoc[]
 include::{kib-repo-dir}/settings/infrastructure-ui-settings.asciidoc[]
-include::{kib-repo-dir}/settings/ml-settings.asciidoc[]
 include::{kib-repo-dir}/settings/monitoring-settings.asciidoc[]
 include::{kib-repo-dir}/settings/reporting-settings.asciidoc[]
 include::secure-settings.asciidoc[]

docs/user/plugins.asciidoc

@@ -145,23 +145,6 @@ You can also remove a plugin manually by deleting the plugin's subdirectory unde
 
 NOTE: Removing a plugin will result in an "optimize" run which will delay the next start of {kib}.
 
-[float]
-[[disable-plugin]]
-== Disable plugins
-
-deprecated:[7.16.0,"In 8.0 and later, this setting will only be supported for a subset of plugins that have opted in to the behavior."]
-
-Use the following command to disable a plugin:
-
-[source,shell]
------------
-./bin/kibana --<plugin ID>.enabled=false <1>
------------
-
-NOTE: Disabling or enabling a plugin will result in an "optimize" run which will delay the start of {kib}.
-
-<1> You can find a plugin's plugin ID as the value of the `name` property in the plugin's `kibana.json` file.
-
 [float]
 [[configure-plugin-manager]]
 == Configure the plugin manager