Skip to content

Commit

Permalink
Remove extra notable-breaking-changes tag in docs.
Browse files Browse the repository at this point in the history
  • Loading branch information
lukeelmers committed Oct 15, 2021
1 parent a7912a1 commit 577400b
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions docs/migration/migrate_8_0.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -30,19 +31,16 @@ 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.

// tag::notable-breaking-changes[]
[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.
Expand Down

0 comments on commit 577400b

Please sign in to comment.