Merge branch 'master' into ml-move-validation-message-parsing-to-client

Author: walterra

.eslintrc.js

@@ -794,6 +794,7 @@ module.exports = {
     {
       files: ['x-pack/plugins/fleet/**/*.{js,mjs,ts,tsx}'],
       rules: {
+        '@typescript-eslint/consistent-type-imports': 'error',
         'import/order': [
           'warn',
           {

api_docs/ml.json

@@ -5498,17 +5498,11 @@
         "type": "Function",
         "children": [
           {
-            "type": "CompoundType",
+            "type": "Any",
             "label": "error",
-            "isRequired": false,
+            "isRequired": true,
             "signature": [
-              {
-                "pluginId": "ml",
-                "scope": "common",
-                "docId": "kibMlPluginApi",
-                "section": "def-common.ErrorType",
-                "text": "ErrorType"
-              }
+              "any"
             ],
             "description": [],
             "source": {
@@ -5518,9 +5512,7 @@
           }
         ],
         "signature": [
-          "(error: ",
-          "ErrorType",
-          ") => string"
+          "(error: any) => string"
         ],
         "description": [],
         "label": "extractErrorMessage",

api_docs/monitoring.json

@@ -46,6 +46,34 @@
             "signature": [
               "() => void"
             ]
+          },
+          {
+            "tags": [],
+            "id": "def-server.IBulkUploader.start",
+            "type": "Function",
+            "label": "start",
+            "description": [],
+            "source": {
+              "path": "x-pack/plugins/monitoring/server/types.ts",
+              "lineNumber": 95
+            },
+            "signature": [
+              "() => void"
+            ]
+          },
+          {
+            "tags": [],
+            "id": "def-server.IBulkUploader.handleNotEnabled",
+            "type": "Function",
+            "label": "handleNotEnabled",
+            "description": [],
+            "source": {
+              "path": "x-pack/plugins/monitoring/server/types.ts",
+              "lineNumber": 96
+            },
+            "signature": [
+              "() => void"
+            ]
           }
         ],
         "source": {
@@ -106,7 +134,7 @@
           "description": [],
           "source": {
             "path": "x-pack/plugins/monitoring/server/types.ts",
-            "lineNumber": 98
+            "lineNumber": 100
           },
           "signature": [
             "() => any"
@@ -115,7 +143,7 @@
       ],
       "source": {
         "path": "x-pack/plugins/monitoring/server/types.ts",
-        "lineNumber": 97
+        "lineNumber": 99
       },
       "lifecycle": "setup",
       "initialIsOpen": true

docs/action-type-template.asciidoc

@@ -1,10 +1,10 @@
 [[<ACTION-TYPE>-action-type]]
-=== <ACTION-TYPE> action
+=== <ACTION-TYPE> connector and action
 ++++
 <titleabbrev><ACTION-TYPE></titleabbrev>
 ++++
 
-Include a short description of the action type.
+Include a short description of the connector type.
 
 [float]
 [[<ACTION-TYPE>-connector-configuration]]
@@ -13,24 +13,24 @@ Include a short description of the action type.
 <ACTION-TYPE> connectors have the following configuration properties.
 
 ////
-List of user-facing connector configurations. This should align with the fields available in the Create connector flyout form for this action type.
+List of user-facing connector configurations. This should align with the fields available in the Create connector flyout form for this connector type.
 ////
 
 Property1:: A short description of this property.
 Property2:: A short description of this property with format hints. This can be specified in `this specific format`.
 
 [float]
 [[Preconfigured-<ACTION-TYPE>-configuration]]
-==== Preconfigured action type
+==== Preconfigured connector type
 
 ////
-Example preconfigured format for this action type
+Example preconfigured format for this connector type
 ////
 
 [source,text]
 --
  my-<ACTION-TYPE>:
-   name: preconfigured-<ACTION-TYPE>-action-type
+   name: preconfigured-<ACTION-TYPE>-connector-type
    actionTypeId: .<ACTION-TYPE>
    config:
      property1: value1
@@ -39,25 +39,23 @@ Example preconfigured format for this action type
      property3: value3
 --
 
-[float]
-[[<ACTION-TYPE>-connector-config-properties]]
 ////
 List of properties from the ConfigSchema and SecretsSchema for this action type.
 ////
-Config defines information for the action type.
+Config defines information for the connector type.
 
 `property1`:: A short description of this property.
 `property2`:: A short descriptionn of this property.
 
-Secrets defines sensitive information for the action type.
+Secrets defines sensitive information for the connector type.
 
 `property3`:: A short descriptionn of this property.
 
 [float]
 [[<ACTION-TYPE>-action-configuration]]
 ==== Action configuration
 
-<ACTION-TYPE> actions have the following configuration properties.
+<ACTION-TYPE> actions have the following properties.
 
 ////
 List of user-facing action configurations. This should align with the fields available in the Action section of the Create/Update alert flyout.

docs/alert-type-template.asciidoc

@@ -142,6 +142,10 @@ to link individual managment section into it. This plugin does not contain any i
 management section itself.
 
 
+|{kib-repo}blob/{branch}/src/plugins/maps_ems/README.md[mapsEms]
+|Configuration of kibana-wide EMS settings and some higher level utilities.
+
+
 |{kib-repo}blob/{branch}/src/plugins/maps_legacy/README.md[mapsLegacy]
 |Internal objects used by the Coordinate, Region, and Vega visualizations.
 

docs/developer/plugin-list.asciidoc

@@ -2,14 +2,12 @@
 [[connector-management]]
 === Managing Connectors
 
-beta[]
-
-Alerts use *Connectors* to route actions to different destinations like log files, ticketing systems, and messaging tools. While each {kib} app can offer their own types of alerts, they typically share connectors. The *Connectors* tab offers a central place to view and manage all the connectors in the current space.
+Rules use *Connectors* to route actions to different destinations like log files, ticketing systems, and messaging tools. While each {kib} app can offer their own types of rules, they typically share connectors. The *Connectors* tab offers a central place to view and manage all the connectors in the current space.
 
 For more information on connectors and the types of actions available see <<action-types>>.
 
 [role="screenshot"]
-image::images/connector-listing.png[Example connector listing in the Alerts and Actions UI]
+image::images/connector-listing.png[Example connector listing in the Rules and Connectors UI]
 
 
 [float]
@@ -21,15 +19,10 @@ The *Connectors* tab lists all connectors in the current space. The *search bar*
 image::images/connector-filter-by-search.png[Filtering the connector list using the search bar]
 
 
-The *type* dropdown also lets you filter to a subset of action types.
-
-[role="screenshot"]
-image::images/connector-filter-by-type.png[Filtering the connector list by types of actions]
-
-The *Actions* column indicates the number of actions that reference the connector. This count helps you confirm a connector is unused before you delete it, and tells you how many actions will be affected when a connector is modified.
+The *type* dropdown also lets you filter to a subset of connector types.
 
 [role="screenshot"]
-image::images/connector-action-count.png[Filtering the connector list by types of actions]
+image::images/connector-filter-by-type.png[Filtering the connector list by types of connectors]
 
 You can delete individual connectors using the trash icon. Connectors can also be deleted in bulk by multi-selecting them and clicking the *Delete* button to the left of the search box. 
 
@@ -44,4 +37,4 @@ When this happens the action will fail to execute, and appear as errors in the {
 
 ==== Creating a new connector
 
-New connectors can be created by clicking the *Create connector* button, which will guide you to select the type of connector and configure it's properties. Refer to <<action-types>> for the types of connectors available and how to configure them. Once you create a connector it will be made available to you anytime you set up an action in the current space.
+New connectors can be created by clicking the *Create connector* button, which will guide you to select the type of connector and configure its properties. Refer to <<action-types>> for the types of connectors available and how to configure them. Once you create a connector it will be made available to you anytime you set up an action in the current space.