maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[DOCS] Removes X-Pack Breaking Changes page (#18755)

Browse source
This commit is contained in:
Lisa Cawley 2018-05-04 12:27:42 -07:00 committed by GitHub
parent b64bf90313
commit 255085f37d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 53 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
docs/migration/migrate_6_0.asciidoc
View file

@ -93,3 +93,25 @@ This is no longer the case. Now, only commas are a valid query separator: e.g. `
*Details:* Replaced `Coordinate Map - Heatmap` configuration controls `Radius`, `Blur`, `Maximum Zoom`, and `Minimum opacity` with a single control, `Cluster size`.
*Impact:* No change is required for existing Coordinate Map visualizations, `Cluster size` will be set to the default value. `Cluster size` may need to be adjusted as needed.
[float]
=== {reporting}
* When {security} is enabled, reports will only be accessible to the user that created them.
* When {security} is enabled, user authorization is controlled by the
`xpack.reporting.roles.allow` setting in the `kibana.yml` which defaults to
`['reporting_user']`. Users will no longer have access to the underlying {reporting}
indices in {es} when assigned to the built-in `reporting_user` role. If using
custom reporting roles, the privileges to the indices will need to be removed, and the
role will need to be added to the `xpack-reporting.roles.allow` setting.
[float]
=== {watcher}
* The watch `_status` field has been renamed to `status`, as underscores in
field names will not be allowed.
* The built-in HTTP client used in webhooks, the http input and the http email
attachment has been replaced. This results in the need to always escape all
parts of an URL.
* The new built-in HTTP client also enforces a maximum request size, which
defaults to 10mb.

53
x-pack/docs/en/release-notes/breaking-changes-xpack.asciidoc
View file

@ -1,53 +0,0 @@
[role="xpack"]
[[breaking-changes-xkb]]
= {xpack} Breaking Changes
[partintro]
--
This section summarizes the changes that you need to be aware of when migrating
your application from one version of {xpack} to another.
* <<breaking-6.1.0-xkb>>
//* <<breaking-6.0.1-xkb>>
* <<breaking-6.0.0-xkb>>
* <<breaking-changes,{kib} Breaking Changes>>
* {ref}/breaking-changes.html[{es} {xpack} Breaking Changes]
* {logstash-ref}/breaking-changes-xls.html[Logstash {xpack} Breaking Changes]
--
[role="xpack"]
[[breaking-6.1.0-xkb]]
== {xpack} Breaking changes in 6.1.0
No breaking changes have been made (yet).
////
[role="xpack"]
[[breaking-6.0.1-xkb]]
== {xpack} Breaking changes in 6.0.1
No breaking changes have been made (yet).
////
[role="xpack"]
[[breaking-6.0.0-xkb]]
== {xpack} Breaking Changes in 6.0.0
Reporting::
* When {security} is enabled, reports will only be accessible to the user that created them.
* When {security} is enabled, user authorization is controlled by the
`xpack.reporting.roles.allow` setting in the `kibana.yml` which defaults to
`['reporting_user']`. Users will no longer have access to the underlying {reporting}
indices in {es} when assigned to the built-in `reporting_user` role. If using
custom reporting roles, the privileges to the indices will need to be removed, and the
role will need to be added to the `xpack-reporting.roles.allow` setting.
Watcher::
* The watch `_status` field has been renamed to `status`, as underscores in
field names will not be allowed.
* The built-in HTTP client used in webhooks, the http input and the http email
attachment has been replaced. This results in the need to always escape all
parts of an URL.
* The new built-in HTTP client also enforces a maximum request size, which
defaults to 10mb.