Merge remote-tracking branch 'upstream/master' into task/hostlist-pagination

Author: parkiino

.eslintrc.js

@@ -96,7 +96,7 @@ module.exports = {
       },
     },
     {
-      files: ['x-pack/legacy/plugins/cross_cluster_replication/**/*.{js,ts,tsx}'],
+      files: ['x-pack/plugins/cross_cluster_replication/**/*.{js,ts,tsx}'],
       rules: {
         'jsx-a11y/click-events-have-key-events': 'off',
       },

.sass-lint.yml

@@ -9,6 +9,7 @@ files:
     - 'x-pack/legacy/plugins/canvas/**/*.s+(a|c)ss'
     - 'x-pack/plugins/triggers_actions_ui/**/*.s+(a|c)ss'
     - 'x-pack/plugins/lens/**/*.s+(a|c)ss'
+    - 'x-pack/plugins/cross_cluster_replication/**/*.s+(a|c)ss'
     - 'x-pack/legacy/plugins/maps/**/*.s+(a|c)ss'
     - 'x-pack/plugins/maps/**/*.s+(a|c)ss'
   ignore:

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.datapublicpluginstart.actions.md

@@ -8,6 +8,7 @@
 
 ```typescript
 actions: {
-        createFiltersFromEvent: typeof createFiltersFromEvent;
+        createFiltersFromValueClickAction: typeof createFiltersFromValueClickAction;
+        createFiltersFromRangeSelectAction: typeof createFiltersFromRangeSelectAction;
     };
 ```

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.datapublicpluginstart.md

@@ -14,7 +14,7 @@ export interface DataPublicPluginStart
 
 |  Property | Type | Description |
 |  --- | --- | --- |
-|  [actions](./kibana-plugin-plugins-data-public.datapublicpluginstart.actions.md) | <code>{</code><br/><code>        createFiltersFromEvent: typeof createFiltersFromEvent;</code><br/><code>    }</code> |  |
+|  [actions](./kibana-plugin-plugins-data-public.datapublicpluginstart.actions.md) | <code>{</code><br/><code>        createFiltersFromValueClickAction: typeof createFiltersFromValueClickAction;</code><br/><code>        createFiltersFromRangeSelectAction: typeof createFiltersFromRangeSelectAction;</code><br/><code>    }</code> |  |
 |  [autocomplete](./kibana-plugin-plugins-data-public.datapublicpluginstart.autocomplete.md) | <code>AutocompleteStart</code> |  |
 |  [fieldFormats](./kibana-plugin-plugins-data-public.datapublicpluginstart.fieldformats.md) | <code>FieldFormatsStart</code> |  |
 |  [indexPatterns](./kibana-plugin-plugins-data-public.datapublicpluginstart.indexpatterns.md) | <code>IndexPatternsContract</code> |  |

docs/development/plugins/data/public/kibana-plugin-plugins-data-public.fieldformats.md

@@ -10,7 +10,7 @@
 fieldFormats: {
     FieldFormat: typeof FieldFormat;
     FieldFormatsRegistry: typeof FieldFormatsRegistry;
-    serialize: (agg: import("./search").AggConfig) => import("../../expressions/common").SerializedFieldFormat<object>;
+    serialize: (agg: import("./search").AggConfig) => import("../../expressions").SerializedFieldFormat<object>;
     DEFAULT_CONVERTER_COLOR: {
         range: string;
         regex: string;

docs/development/plugins/data/server/kibana-plugin-plugins-data-server.fieldformats.md

@@ -10,7 +10,7 @@
 fieldFormats: {
     FieldFormatsRegistry: typeof FieldFormatsRegistry;
     FieldFormat: typeof FieldFormat;
-    serializeFieldFormat: (agg: import("../public/search").AggConfig) => import("../../expressions/common").SerializedFieldFormat<object>;
+    serializeFieldFormat: (agg: import("../public/search").AggConfig) => import("../../expressions").SerializedFieldFormat<object>;
     BoolFormat: typeof BoolFormat;
     BytesFormat: typeof BytesFormat;
     ColorFormat: typeof ColorFormat;

docs/user/alerting/action-types/email.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[email-action-type]]
-== Email action type
+=== Email action
 
 The email action type uses the SMTP protocol to send mail message, using an integration of https://nodemailer.com/[Nodemailer]. Email message text is sent as both plain text and html text.
 
@@ -10,11 +10,11 @@ The email action type uses the SMTP protocol to send mail message, using an inte
 
 Email connectors have the following configuration properties:
 
-Name::      The name of the connector. The name is used to identify a  connector in the management UI connector listing, or in the connector list when configuring an action. 
+Name::      The name of the connector. The name is used to identify a  connector in the management UI connector listing, or in the connector list when configuring an action.
 Sender::    The from address for all emails sent with this connector, specified in `user@host-name` format.
-Host::      Host name of the service provider. If you are using the <<action-settings, `xpack.actions.whitelistedHosts`>> setting, make sure this hostname is whitelisted. 
+Host::      Host name of the service provider. If you are using the <<action-settings, `xpack.actions.whitelistedHosts`>> setting, make sure this hostname is whitelisted.
 Port::      The port to connect to on the service provider.
-Secure::    If true the connection will use TLS when connecting to the service provider. See https://nodemailer.com/smtp/#tls-options[nodemailer TLS documentation] for more information.  
+Secure::    If true the connection will use TLS when connecting to the service provider. See https://nodemailer.com/smtp/#tls-options[nodemailer TLS documentation] for more information.
 Username::  username for 'login' type authentication.
 Password::  password for 'login' type authentication.
 
@@ -26,4 +26,4 @@ Email actions have the following configuration properties:
 
 To, CC, BCC::    Each is a list of addresses. Addresses can be specified in `user@host-name` format, or in `name <user@host-name>` format. One of To, CC, or BCC must contain an entry.
 Subject::       The subject line of the email.
-Message::       The message text of the email. Markdown format is supported.
+Message::       The message text of the email. Markdown format is supported.

docs/user/alerting/action-types/index.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[index-action-type]]
-== Index action type
+=== Index action
 
 The index action type will index a document into {es}.
 
@@ -21,4 +21,4 @@ Execution time field::  This field will be automatically set to the time the ale
 
 Index actions have the following properties:
 
-Document::  The document to index in json format.
+Document::  The document to index in json format.

docs/user/alerting/action-types/pagerduty.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[pagerduty-action-type]]
-== PagerDuty action type
+=== PagerDuty action
 
 The PagerDuty action type uses the https://v2.developer.pagerduty.com/docs/events-api-v2[v2 Events API] to trigger, acknowledge, and resolve PagerDuty alerts.
 
@@ -10,7 +10,7 @@ The PagerDuty action type uses the https://v2.developer.pagerduty.com/docs/event
 
 [float]
 [[pagerduty-benefits]]
-=== PagerDuty + Elastic integration benefits
+==== PagerDuty + Elastic integration benefits
 
 By integrating PagerDuty with alerts, you can:
 
@@ -20,15 +20,15 @@ By integrating PagerDuty with alerts, you can:
 
 [float]
 [[pagerduty-how-it-works]]
-==== How it works
+===== How it works
 
 {kib} allows you to create alerts to notify you of a significant move
 in your dataset.
 You can create alerts for all your Observability, Security, and Elastic Stack use cases.
 Alerts will trigger a new incident on the corresponding PagerDuty service.
 
 [float]
-==== Requirements
+===== Requirements
 
 In the `kibana.yml` configuration file, you must add the <<general-alert-action-settings, saved objects encryption setting>>.
 This is required to encrypt parameters that must be secured, for example PagerDuty’s integration key.
@@ -47,18 +47,17 @@ review the <<action-settings, Actions settings>> that are available to you.
 
 [float]
 [[pagerduty-support]]
-==== Support
+===== Support
 If you need help with this integration, get in touch with the {kib} team by visiting
 https://support.elastic.co[support.elastic.co] or by using the *Ask Elastic* option in the {kib} Help menu.
 You can also select the {kib} category at https://discuss.elastic.co/[discuss.elastic.co].
 
 [float]
 [[pagerduty-integration-walkthrough]]
-==== Integration with PagerDuty walkthrough
+===== Integration with PagerDuty walkthrough
 
-[float]
 [[pagerduty-in-pagerduty]]
-===== In PagerDuty
+*In PagerDuty*
 
 . From the *Configuration* menu, select *Services*.
 . Add an integration to a service:
@@ -83,9 +82,8 @@ image::user/alerting/images/pagerduty-integration.png[PagerDuty Integrations tab
 
 . Save this key, as you will use it when you configure the integration with Elastic in the next section.
 
-[float]
 [[pagerduty-in-elastic]]
-===== In Elastic
+*In Elastic*
 
 . Create a PagerDuty Connector in Kibana.  You can:
 +
@@ -117,7 +115,7 @@ https://v2.developer.pagerduty.com/v2/docs/send-an-event-events-api-v2[API v2 do
 
 [float]
 [[pagerduty-uninstall]]
-==== How to uninstall
+===== How to uninstall
 To remove a PagerDuty connector from an alert, simply remove it
 from the *Actions* section of that alert, using the remove (x) icon.
 This will disable the integration for the particular alert.
@@ -129,7 +127,7 @@ This is an irreversible action and impacts all alerts that use this connector.
 
 [float]
 [[pagerduty-connector-configuration]]
-=== Connector configuration
+==== Connector configuration
 
 PagerDuty connectors have the following configuration properties:
 
@@ -139,7 +137,7 @@ Routing Key::   A 32 character PagerDuty Integration Key for an integration on a
 
 [float]
 [[pagerduty-action-configuration]]
-=== Action configuration
+==== Action configuration
 
 PagerDuty actions have the following properties:
 

docs/user/alerting/action-types/server-log.asciidoc

@@ -1,6 +1,6 @@
 [role="xpack"]
 [[server-log-action-type]]
-== Server log action type
+=== Server log action
 
 This action type writes and entry to the {kib} server log.
 
@@ -18,4 +18,4 @@ Name::      The name of the connector. The name is used to identify a  connector
 
 Server log actions have the following properties:
 
-Message::   The message to log. 
+Message::   The message to log.