[8.6] Upgrade EUI to v67.1.10

.buildkite/disabled_jest_configs.json

@@ -1,4 +1,5 @@
 [
   "x-pack/plugins/triggers_actions_ui/jest.config.js",
-  "x-pack/plugins/watcher/jest.config.js"
+  "x-pack/plugins/watcher/jest.config.js",
+  "src/core/server/integration_tests/ui_settings/jest.integration.config.js"
 ]

.buildkite/pipeline-utils/ci-stats/pick_test_group_run_order.ts

@@ -234,6 +234,7 @@ export async function pickTestGroupRunOrder() {
     ? globby.sync(['**/jest.integration.config.js', '!**/__fixtures__/**'], {
         cwd: process.cwd(),
         absolute: false,
+        ignore: DISABLED_JEST_CONFIGS,
       })
     : [];
 

docs/api-generated/cases/case-apis-passthru.asciidoc

@@ -2077,13 +2077,13 @@ Any modifications made to this file will be overwritten.
   </div>
   <div class="model">
     <h3><a name="alert_identifiers"><code>alert_identifiers</code> - Alert identifiers</a> <a class="up" href="#__Models">Up</a></h3>
-    <div class='model-description'>The alert identifier. It is required only when <code>type</code> is <code>alert</code>. If it is an array, <code>index</code> must also be an array with the same length or number of elements. This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.</div>
+    <div class='model-description'>The alert identifiers. It is required only when <code>type</code> is <code>alert</code>. You can use an array of strings to add multiple alerts to a case, provided that they all relate to the same rule; <code>index</code> must also be an array with the same length or number of elements. Adding multiple alerts in this manner is recommended rather than calling the API multiple times. This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.</div>
     <div class="field-items">
           </div>  <!-- field-items -->
   </div>
   <div class="model">
     <h3><a name="alert_indices"><code>alert_indices</code> - Alert indices</a> <a class="up" href="#__Models">Up</a></h3>
-    <div class='model-description'>The alert index. It is required only when <code>type</code> is <code>alert</code>. If it is an array, <code>alertId</code> must also be an array with the same length or number of elements. This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.</div>
+    <div class='model-description'>The alert indices. It is required only when <code>type</code> is <code>alert</code>.  If you are adding multiple alerts to a case, use an array of strings; the position of each index name in the array must match the position of the corresponding alert identifier in the <code>alertId</code> array. This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.</div>
     <div class="field-items">
           </div>  <!-- field-items -->
   </div>
@@ -2663,7 +2663,7 @@ Any modifications made to this file will be overwritten.
   </div>
   <div class="model">
     <h3><a name="rule"><code>rule</code> - Alerting rule</a> <a class="up" href="#__Models">Up</a></h3>
-    <div class='model-description'>The rule that is associated with the alert. It is required only when <code>type</code> is <code>alert</code>. This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.</div>
+    <div class='model-description'>The rule that is associated with the alerts. It is required only when <code>type</code> is <code>alert</code>. This functionality is in technical preview and may be changed or removed in a future release. Elastic will apply best effort to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.</div>
     <div class="field-items">
       <div class="param">id (optional)</div><div class="param-desc"><span class="param-type"><a href="#string">String</a></span> The rule identifier. </div>
 <div class="param">name (optional)</div><div class="param-desc"><span class="param-type"><a href="#string">String</a></span> The rule name. </div>

docs/api/actions-and-connectors.asciidoc

@@ -1,27 +1,26 @@
 [[actions-and-connectors-api]]
 == Action and connector APIs
 
-Manage Actions and Connectors.
-
 The following connector APIs are available:
 
-* <<get-connector-api, Get connector API>> to retrieve a single connector by ID
+* <<get-connector-api,Get connector API>> to retrieve a single connector by ID
 
-* <<get-all-connectors-api, Get all connectors API>> to retrieve all connectors
+* <<get-all-connectors-api,Get all connectors API>> to retrieve all connectors
 
-* <<list-connector-types-api, List all connector types API>> to retrieve a list of all connector types
+* <<list-connector-types-api,List all connector types API>> to retrieve a list of all connector types
 
-* <<create-connector-api, Create connector API>> to create connectors
+* <<create-connector-api,Create connector API>> to create connectors
 
-* <<update-connector-api, Update connector API>> to update the attributes for an existing connector
+* <<update-connector-api,Update connector API>> to update the attributes for an existing connector
 
-* <<execute-connector-api, Execute connector API>> to execute a connector by ID
+* <<execute-connector-api,Run connector API>> to execute a connector by ID
 
-* <<delete-connector-api, Delete connector API>> to delete a connector by ID
+* <<delete-connector-api,Delete connector API>> to delete a connector by ID
 
 For deprecated APIs, refer to <<actions-and-connectors-legacy-apis>>.
 
-For information about the actions and connectors that {kib} supports, refer to <<action-types,Action and connector types>>.
+For information about the actions and connectors that {kib} supports, refer to
+<<action-types>>.
 
 include::actions-and-connectors/create.asciidoc[leveloffset=+1]
 include::actions-and-connectors/delete.asciidoc[leveloffset=+1]

docs/api/actions-and-connectors/create.asciidoc

@@ -15,9 +15,8 @@ Creates a connector.
 
 === {api-prereq-title}
 
-You must have `all` privileges for the *Actions and Connectors* feature in the
-*Management* section of the
-<<kibana-feature-privileges,{kib} feature privileges>>.
+You must have `all` privileges for the *{connectors-feature}* feature in the
+*Management* section of the <<kibana-feature-privileges,{kib} feature privileges>>.
 
 [[create-connector-api-path-params]]
 === {api-path-parms-title}

docs/api/actions-and-connectors/delete.asciidoc

@@ -19,7 +19,7 @@ WARNING: When you delete a connector, _it cannot be recovered_.
 [discrete]
 === {api-prereq-title}
 
-You must have `all` privileges for the *Actions and Connectors* feature in the
+You must have `all` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 

docs/api/actions-and-connectors/execute.asciidoc

@@ -16,7 +16,7 @@ Runs a connector by ID.
 [[execute-connector-api-prereq]]
 === {api-prereq-title}
 
-You must have `read` privileges for the *Actions and Connectors* feature in the
+You must have `read` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 
@@ -60,8 +60,7 @@ refer to <<action-types>>.
 `documents`::
 (Required, array of objects) The documents to index in JSON format.
 
-For more information, refer to
-{kibana-ref}/index-action-type.html[Index connector and action].
+For more information, refer to <<index-action-type>>.
 =====
 
 .Jira connectors
@@ -158,10 +157,124 @@ the knowledge base.
 =======
 ======
 
-For more information, refer to
-{kibana-ref}/jira-action-type.html[{jira} connector and action].
+For more information, refer to <<jira-action-type>>.
 =====
 
+.{opsgenie} connectors
+[%collapsible%open]
+=====
+`subAction`::
+(Required, string) The action to test. Valid values include: `createAlert` and
+`closeAlert`.
+
+`subActionParams`::
+(Required, object) The set of configuration properties, which vary depending on
+the `subAction` value.
++
+.Properties when `subAction` is `createAlert`
+[%collapsible%open]
+======
+`actions`::::
+(Optional, array of strings) The custom actions available to the alert.
+
+`alias`::::
+(Optional, string) The unique identifier used for alert de-duplication in {opsgenie}.
+
+`description`::::
+(Optional, string) A description that provides detailed information about the alert.
+
+`details`::::
+(Optional, object) The custom properties of the alert. For example:
+`{"key1":"value1","key2":"value2"}`.
+
+`entity`::::
+(Optional, string) The domain of the alert. For example, the application or server
+name.
+
+`message`::::
+(Required, string) The alert message.
+
+`note`::::
+(Optional, string) Additional information for the alert.
+
+`priority`::::
+(Optional, string) The priority level for the alert. Valid values are: `P1`,
+`P2`, `P3`, `P4`, and `P5`.
+
+`responders`::::
+(Optional, array of objects) The entities to receive notifications about the
+alert. If `type` is `user`, either `id` or `username` is required. If `type` is
+`team`, either `id` or `name` is required.
++
+.Properties of `responders` objects
+[%collapsible%open]
+=======
+`id`::::
+(Required^*^, string) The identifier for the entity. 
+
+`name`::::
+(Required^*^, string) The name of the entity.
+
+`type`::::
+(Required, string) Valid values are `escalation`, `schedule`, `team`, and `user`.
+
+`username`::::
+(Required^*^, string) A valid email address for the user.
+=======
+
+`source`::::
+(Optional, string) The display name for the source of the alert.
+
+`tags`::::
+(Optional, array of strings) The tags for the alert.
+
+`user`::::
+(Optional, string) The display name for the owner.
+
+`visibleTo`::::
+(Optional, array of objects) The teams and users that the alert will be visible
+to without sending a notification. Only one of `id`, `name`, or `username` is
+required.
++
+.Properties of `visibleTo` objects
+[%collapsible%open]
+=======
+`id`::::
+(Required^*^, string) The identifier for the entity.
+
+`name`::::
+(Required^*^, string) The name of the entity.
+
+`type`::::
+(Required, string) Valid values are `team` and `user`.
+
+`username`::::
+(Required^*^, string) The user name. This property is required only when the
+`type` is `user`.
+=======
+======
++
+.Properties when `subAction` is `closeAlert`
+[%collapsible%open]
+======
+`alias`::::
+(Required, string) The unique identifier used for alert de-duplication in {opsgenie}.
+The alias must match the value used when creating the alert.
+
+`note`::::
+(Optional, string) Additional information for the alert.
+
+`source`::::
+(Optional, string) The display name for the source of the alert.
+
+`user`::::
+(Optional, string) The display name for the owner.
+======
+
+For more information, refer to <<opsgenie-action-type>>.
+=====
+
+
 .{sn-itom} connectors
 [%collapsible%open]
 =====

docs/api/actions-and-connectors/get.asciidoc

@@ -17,7 +17,7 @@ Retrieves a connector by ID.
 [discrete]
 === {api-prereq-title}
 
-You must have `read` privileges for the *Actions and Connectors* feature in the
+You must have `read` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 

docs/api/actions-and-connectors/get_all.asciidoc

@@ -17,7 +17,7 @@ Retrieves all connectors.
 [discrete]
 === {api-prereq-title}
 
-You must have `read` privileges for the *Actions and Connectors* feature in the
+You must have `read` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 

docs/api/actions-and-connectors/update.asciidoc

@@ -16,7 +16,7 @@ Updates the attributes for a connector.
 [discrete]
 === {api-prereq-title}
 
-You must have `all` privileges for the *Actions and Connectors* feature in the
+You must have `all` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 

docs/api/alerting/create_rule.asciidoc

@@ -21,7 +21,7 @@ the `consumer` and `rule_type_id` of the rules you're creating. For example, the
 *Management* > *Stack Rules* feature, *Analytics* > *Discover* and *{ml-app}*
 features, *{observability}*, and *Security* features. If the rule has `actions`,
 you must also have `read` privileges for the *Management* >
-*Actions and Connectors* feature. For more details, refer to
+*{connectors-feature}* feature. For more details, refer to
 <<kibana-feature-privileges>>.
 
 === {api-description-title}

docs/api/alerting/mute_alert.asciidoc

@@ -20,7 +20,7 @@ the `consumer` and `rule_type_id` of the rules you're creating. For example, the
 *Management* > *Stack Rules* feature, *Analytics* > *Discover* and *{ml-app}*
 features, *{observability}*, and *Security* features. If the rule has `actions`,
 you must also have `read` privileges for the *Management* >
-*Actions and Connectors* feature. For more details, refer to
+*{connectors-feature}* feature. For more details, refer to
 <<kibana-feature-privileges>>.
 
 [[mute-alert-api-path-params]]

docs/api/alerting/mute_all_alerts.asciidoc

@@ -20,7 +20,7 @@ the `consumer` and `rule_type_id` of the rules you're creating. For example, the
 *Management* > *Stack Rules* feature, *Analytics* > *Discover* and *{ml-app}*
 features, *{observability}*, and *Security* features. If the rule has `actions`,
 you must also have `read` privileges for the *Management* >
-*Actions and Connectors* feature. For more details, refer to
+*{connectors-feature}* feature. For more details, refer to
 <<kibana-feature-privileges>>.
 
 === {api-description-title}

docs/api/alerting/unmute_alert.asciidoc

@@ -20,7 +20,7 @@ the `consumer` and `rule_type_id` of the rules you're creating. For example, the
 *Management* > *Stack Rules* feature, *Analytics* > *Discover* and *{ml-app}*
 features, *{observability}*, and *Security* features. If the rule has `actions`,
 you must also have `read` privileges for the *Management* >
-*Actions and Connectors* feature. For more details, refer to
+*{connectors-feature}* feature. For more details, refer to
 <<kibana-feature-privileges>>.
 
 [[unmute-alert-api-path-params]]

docs/api/alerting/unmute_all_alerts.asciidoc

@@ -20,7 +20,7 @@ the `consumer` and `rule_type_id` of the rules you're creating. For example, the
 *Management* > *Stack Rules* feature, *Analytics* > *Discover* and *{ml-app}*
 features, *{observability}*, and *Security* features. If the rule has `actions`,
 you must also have `read` privileges for the *Management* >
-*Actions and Connectors* feature. For more details, refer to
+*{connectors-feature}* feature. For more details, refer to
 <<kibana-feature-privileges>>.
 
 === {api-description-title}

docs/api/alerting/update_rule.asciidoc

@@ -20,7 +20,7 @@ the `consumer` and `rule_type_id` of the rule you're updating. For example, the
 *Management* > *Stack Rules* feature, *Analytics* > *Discover* and *{ml-app}*
 features, *{observability}*, or *Security* features. If the rule has
 `actions`, you must also have `read` privileges for the *Management* >
-*Actions and Connectors* feature. For more details, refer to
+*{connectors-feature}* feature. For more details, refer to
 <<kibana-feature-privileges>>.
 
 === {api-description-title}

docs/api/cases/cases-api-add-comment.asciidoc

@@ -39,22 +39,28 @@ default space is used.
 === {api-request-body-title}
 
 `alertId`::
-(Required*, string or array of strings) The alert identifier. It is required
-only when `type` is `alert`. If it is an array, `index` must also be an array. preview:[]
+(Required*, string or array of strings) The alert identifiers. It is required
+only when `type` is `alert`. You can use an array of strings to add multiple
+alerts to a case, provided that they all relate to the same rule; `index` must
+also be an array with the same length or number of elements. Adding multiple
+alerts in this manner is recommended rather than calling the API multiple times.
+preview:[]
 
 `comment`::
 (Required*, string) The new comment. It is required only when `type` is `user`.
 
 `index`::
-(Required*, string or array of strings) The alert index. It is required only
-when `type` is `alert`. If it is an array, `alertId` must also be an array. preview:[]
+(Required*, string or array of strings) The alert indices. It is required only
+when `type` is `alert`. If you are adding multiple alerts to a case, use an array
+of strings; the position of each index name in the array must match the position
+of the corresponding alert identifier in the `alertId` array. preview:[]
 
 `owner`::
 (Required, string) The application that owns the case. Valid values are:
 `cases`, `observability`, or `securitySolution`.
 
 `rule`::
-(Required*, object) The rule that is associated with the alert. It is required
+(Required*, object) The rule that is associated with the alerts. It is required
 only when `type` is `alert`. preview:[]
 +
 .Properties of `rule`

docs/api/cases/cases-api-find-connectors.asciidoc

@@ -24,7 +24,7 @@ For the most up-to-date API details, refer to the
 
 === {api-prereq-title}
 
-You must have `read` privileges for the *Actions and Connectors* feature in the
+You must have `read` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>.
 

docs/api/cases/cases-api-push.asciidoc

@@ -20,7 +20,7 @@ For the most up-to-date API details, refer to the
 
 === {api-prereq-title}
 
-You must have `all` privileges for the *Actions and Connectors* feature in the
+You must have `all` privileges for the *{connectors-feature}* feature in the
 *Management* section of the
 <<kibana-feature-privileges,{kib} feature privileges>>. You must also have `all`
 privileges for the *Cases* feature in the *Management*, *{observability}*, or