elasticsearch 8.17.1__py3-none-any.whl → 8.17.2__py3-none-any.whl

elasticsearch/_async/client/indices.py

@@ -55,8 +55,11 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Add an index block. Limits the operations allowed on an index by blocking specific
-        operation types.
+        .. raw:: html
+
+          <p>Add an index block.
+          Limits the operations allowed on an index by blocking specific operation types.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/index-modules-blocks.html>`_
 
@@ -143,12 +146,15 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get tokens from text analysis. The analyze API performs analysis on a text string
-        and returns the resulting tokens. Generating excessive amount of tokens may cause
-        a node to run out of memory. The `index.analyze.max_token_count` setting enables
-        you to limit the number of tokens that can be produced. If more than this limit
-        of tokens gets generated, an error occurs. The `_analyze` endpoint without a
-        specified index will always use `10000` as its limit.
+        .. raw:: html
+
+          <p>Get tokens from text analysis.
+          The analyze API performs analysis on a text string and returns the resulting tokens.</p>
+          <p>Generating excessive amount of tokens may cause a node to run out of memory.
+          The <code>index.analyze.max_token_count</code> setting enables you to limit the number of tokens that can be produced.
+          If more than this limit of tokens gets generated, an error occurs.
+          The <code>_analyze</code> endpoint without a specified index will always use <code>10000</code> as its limit.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-analyze.html>`_
 
@@ -249,11 +255,15 @@ class IndicesClient(NamespacedClient):
         request: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Clear the cache. Clear the cache of one or more indices. For data streams, the
-        API clears the caches of the stream's backing indices. By default, the clear
-        cache API clears all caches. To clear only specific caches, use the `fielddata`,
-        `query`, or `request` parameters. To clear the cache only of specific fields,
-        use the `fields` parameter.
+        .. raw:: html
+
+          <p>Clear the cache.
+          Clear the cache of one or more indices.
+          For data streams, the API clears the caches of the stream's backing indices.</p>
+          <p>By default, the clear cache API clears all caches.
+          To clear only specific caches, use the <code>fielddata</code>, <code>query</code>, or <code>request</code> parameters.
+          To clear the cache only of specific fields, use the <code>fields</code> parameter.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-clearcache.html>`_
 
@@ -338,44 +348,44 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Clone an index. Clone an existing index into a new index. Each original primary
-        shard is cloned into a new primary shard in the new index. IMPORTANT: Elasticsearch
-        does not apply index templates to the resulting index. The API also does not
-        copy index metadata from the original index. Index metadata includes aliases,
-        index lifecycle management phase definitions, and cross-cluster replication (CCR)
-        follower information. For example, if you clone a CCR follower index, the resulting
-        clone will not be a follower index. The clone API copies most index settings
-        from the source index to the resulting index, with the exception of `index.number_of_replicas`
-        and `index.auto_expand_replicas`. To set the number of replicas in the resulting
-        index, configure these settings in the clone request. Cloning works as follows:
-        * First, it creates a new target index with the same definition as the source
-        index. * Then it hard-links segments from the source index into the target index.
-        If the file system does not support hard-linking, all segments are copied into
-        the new index, which is a much more time consuming process. * Finally, it recovers
-        the target index as though it were a closed index which had just been re-opened.
-        IMPORTANT: Indices can only be cloned if they meet the following requirements:
-        * The index must be marked as read-only and have a cluster health status of green.
-        * The target index must not exist. * The source index must have the same number
-        of primary shards as the target index. * The node handling the clone process
-        must have sufficient free disk space to accommodate a second copy of the existing
-        index. The current write index on a data stream cannot be cloned. In order to
-        clone the current write index, the data stream must first be rolled over so that
-        a new write index is created and then the previous write index can be cloned.
-        NOTE: Mappings cannot be specified in the `_clone` request. The mappings of the
-        source index will be used for the target index. **Monitor the cloning process**
-        The cloning process can be monitored with the cat recovery API or the cluster
-        health API can be used to wait until all primary shards have been allocated by
-        setting the `wait_for_status` parameter to `yellow`. The `_clone` API returns
-        as soon as the target index has been added to the cluster state, before any shards
-        have been allocated. At this point, all shards are in the state unassigned. If,
-        for any reason, the target index can't be allocated, its primary shard will remain
-        unassigned until it can be allocated on that node. Once the primary shard is
-        allocated, it moves to state initializing, and the clone process begins. When
-        the clone operation completes, the shard will become active. At that point, Elasticsearch
-        will try to allocate any replicas and may decide to relocate the primary shard
-        to another node. **Wait for active shards** Because the clone operation creates
-        a new index to clone the shards to, the wait for active shards setting on index
-        creation applies to the clone index action as well.
+        .. raw:: html
+
+          <p>Clone an index.
+          Clone an existing index into a new index.
+          Each original primary shard is cloned into a new primary shard in the new index.</p>
+          <p>IMPORTANT: Elasticsearch does not apply index templates to the resulting index.
+          The API also does not copy index metadata from the original index.
+          Index metadata includes aliases, index lifecycle management phase definitions, and cross-cluster replication (CCR) follower information.
+          For example, if you clone a CCR follower index, the resulting clone will not be a follower index.</p>
+          <p>The clone API copies most index settings from the source index to the resulting index, with the exception of <code>index.number_of_replicas</code> and <code>index.auto_expand_replicas</code>.
+          To set the number of replicas in the resulting index, configure these settings in the clone request.</p>
+          <p>Cloning works as follows:</p>
+          <ul>
+          <li>First, it creates a new target index with the same definition as the source index.</li>
+          <li>Then it hard-links segments from the source index into the target index. If the file system does not support hard-linking, all segments are copied into the new index, which is a much more time consuming process.</li>
+          <li>Finally, it recovers the target index as though it were a closed index which had just been re-opened.</li>
+          </ul>
+          <p>IMPORTANT: Indices can only be cloned if they meet the following requirements:</p>
+          <ul>
+          <li>The index must be marked as read-only and have a cluster health status of green.</li>
+          <li>The target index must not exist.</li>
+          <li>The source index must have the same number of primary shards as the target index.</li>
+          <li>The node handling the clone process must have sufficient free disk space to accommodate a second copy of the existing index.</li>
+          </ul>
+          <p>The current write index on a data stream cannot be cloned.
+          In order to clone the current write index, the data stream must first be rolled over so that a new write index is created and then the previous write index can be cloned.</p>
+          <p>NOTE: Mappings cannot be specified in the <code>_clone</code> request. The mappings of the source index will be used for the target index.</p>
+          <p><strong>Monitor the cloning process</strong></p>
+          <p>The cloning process can be monitored with the cat recovery API or the cluster health API can be used to wait until all primary shards have been allocated by setting the <code>wait_for_status</code> parameter to <code>yellow</code>.</p>
+          <p>The <code>_clone</code> API returns as soon as the target index has been added to the cluster state, before any shards have been allocated.
+          At this point, all shards are in the state unassigned.
+          If, for any reason, the target index can't be allocated, its primary shard will remain unassigned until it can be allocated on that node.</p>
+          <p>Once the primary shard is allocated, it moves to state initializing, and the clone process begins.
+          When the clone operation completes, the shard will become active.
+          At that point, Elasticsearch will try to allocate any replicas and may decide to relocate the primary shard to another node.</p>
+          <p><strong>Wait for active shards</strong></p>
+          <p>Because the clone operation creates a new index to clone the shards to, the wait for active shards setting on index creation applies to the clone index action as well.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-clone-index.html>`_
 
@@ -463,24 +473,23 @@ class IndicesClient(NamespacedClient):
         ] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Close an index. A closed index is blocked for read or write operations and does
-        not allow all operations that opened indices allow. It is not possible to index
-        documents or to search for documents in a closed index. Closed indices do not
-        have to maintain internal data structures for indexing or searching documents,
-        which results in a smaller overhead on the cluster. When opening or closing an
-        index, the master node is responsible for restarting the index shards to reflect
-        the new state of the index. The shards will then go through the normal recovery
-        process. The data of opened and closed indices is automatically replicated by
-        the cluster to ensure that enough shard copies are safely kept around at all
-        times. You can open and close multiple indices. An error is thrown if the request
-        explicitly refers to a missing index. This behaviour can be turned off using
-        the `ignore_unavailable=true` parameter. By default, you must explicitly name
-        the indices you are opening or closing. To open or close indices with `_all`,
-        `*`, or other wildcard expressions, change the` action.destructive_requires_name`
-        setting to `false`. This setting can also be changed with the cluster update
-        settings API. Closed indices consume a significant amount of disk-space which
-        can cause problems in managed environments. Closing indices can be turned off
-        with the cluster settings API by setting `cluster.indices.close.enable` to `false`.
+        .. raw:: html
+
+          <p>Close an index.
+          A closed index is blocked for read or write operations and does not allow all operations that opened indices allow.
+          It is not possible to index documents or to search for documents in a closed index.
+          Closed indices do not have to maintain internal data structures for indexing or searching documents, which results in a smaller overhead on the cluster.</p>
+          <p>When opening or closing an index, the master node is responsible for restarting the index shards to reflect the new state of the index.
+          The shards will then go through the normal recovery process.
+          The data of opened and closed indices is automatically replicated by the cluster to ensure that enough shard copies are safely kept around at all times.</p>
+          <p>You can open and close multiple indices.
+          An error is thrown if the request explicitly refers to a missing index.
+          This behaviour can be turned off using the <code>ignore_unavailable=true</code> parameter.</p>
+          <p>By default, you must explicitly name the indices you are opening or closing.
+          To open or close indices with <code>_all</code>, <code>*</code>, or other wildcard expressions, change the<code> action.destructive_requires_name</code> setting to <code>false</code>. This setting can also be changed with the cluster update settings API.</p>
+          <p>Closed indices consume a significant amount of disk-space which can cause problems in managed environments.
+          Closing indices can be turned off with the cluster settings API by setting <code>cluster.indices.close.enable</code> to <code>false</code>.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-close.html>`_
 
@@ -561,26 +570,27 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Create an index. You can use the create index API to add a new index to an Elasticsearch
-        cluster. When creating an index, you can specify the following: * Settings for
-        the index. * Mappings for fields in the index. * Index aliases **Wait for active
-        shards** By default, index creation will only return a response to the client
-        when the primary copies of each shard have been started, or the request times
-        out. The index creation response will indicate what happened. For example, `acknowledged`
-        indicates whether the index was successfully created in the cluster, `while shards_acknowledged`
-        indicates whether the requisite number of shard copies were started for each
-        shard in the index before timing out. Note that it is still possible for either
-        `acknowledged` or `shards_acknowledged` to be `false`, but for the index creation
-        to be successful. These values simply indicate whether the operation completed
-        before the timeout. If `acknowledged` is false, the request timed out before
-        the cluster state was updated with the newly created index, but it probably will
-        be created sometime soon. If `shards_acknowledged` is false, then the request
-        timed out before the requisite number of shards were started (by default just
-        the primaries), even if the cluster state was successfully updated to reflect
-        the newly created index (that is to say, `acknowledged` is `true`). You can change
-        the default of only waiting for the primary shards to start through the index
-        setting `index.write.wait_for_active_shards`. Note that changing this setting
-        will also affect the `wait_for_active_shards` value on all subsequent write operations.
+        .. raw:: html
+
+          <p>Create an index.
+          You can use the create index API to add a new index to an Elasticsearch cluster.
+          When creating an index, you can specify the following:</p>
+          <ul>
+          <li>Settings for the index.</li>
+          <li>Mappings for fields in the index.</li>
+          <li>Index aliases</li>
+          </ul>
+          <p><strong>Wait for active shards</strong></p>
+          <p>By default, index creation will only return a response to the client when the primary copies of each shard have been started, or the request times out.
+          The index creation response will indicate what happened.
+          For example, <code>acknowledged</code> indicates whether the index was successfully created in the cluster, <code>while shards_acknowledged</code> indicates whether the requisite number of shard copies were started for each shard in the index before timing out.
+          Note that it is still possible for either <code>acknowledged</code> or <code>shards_acknowledged</code> to be <code>false</code>, but for the index creation to be successful.
+          These values simply indicate whether the operation completed before the timeout.
+          If <code>acknowledged</code> is false, the request timed out before the cluster state was updated with the newly created index, but it probably will be created sometime soon.
+          If <code>shards_acknowledged</code> is false, then the request timed out before the requisite number of shards were started (by default just the primaries), even if the cluster state was successfully updated to reflect the newly created index (that is to say, <code>acknowledged</code> is <code>true</code>).</p>
+          <p>You can change the default of only waiting for the primary shards to start through the index setting <code>index.write.wait_for_active_shards</code>.
+          Note that changing this setting will also affect the <code>wait_for_active_shards</code> value on all subsequent write operations.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-create-index.html>`_
 
@@ -653,8 +663,12 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Create a data stream. Creates a data stream. You must have a matching index template
-        with data stream enabled.
+        .. raw:: html
+
+          <p>Create a data stream.
+          Creates a data stream.
+          You must have a matching index template with data stream enabled.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -715,7 +729,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get data stream stats. Retrieves statistics for one or more data streams.
+        .. raw:: html
+
+          <p>Get data stream stats.
+          Retrieves statistics for one or more data streams.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -776,11 +794,15 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Delete indices. Deleting an index deletes its documents, shards, and metadata.
-        It does not delete related Kibana components, such as data views, visualizations,
-        or dashboards. You cannot delete the current write index of a data stream. To
-        delete the index, you must roll over the data stream so a new write index is
-        created. You can then use the delete index API to delete the previous write index.
+        .. raw:: html
+
+          <p>Delete indices.
+          Deleting an index deletes its documents, shards, and metadata.
+          It does not delete related Kibana components, such as data views, visualizations, or dashboards.</p>
+          <p>You cannot delete the current write index of a data stream.
+          To delete the index, you must roll over the data stream so a new write index is created.
+          You can then use the delete index API to delete the previous write index.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-delete-index.html>`_
 
@@ -850,7 +872,11 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Delete an alias. Removes a data stream or index from an alias.
+        .. raw:: html
+
+          <p>Delete an alias.
+          Removes a data stream or index from an alias.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-delete-alias.html>`_
 
@@ -914,8 +940,11 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Delete data stream lifecycles. Removes the data stream lifecycle from a data
-        stream, rendering it not managed by the data stream lifecycle.
+        .. raw:: html
+
+          <p>Delete data stream lifecycles.
+          Removes the data stream lifecycle from a data stream, rendering it not managed by the data stream lifecycle.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams-delete-lifecycle.html>`_
 
@@ -975,7 +1004,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Delete data streams. Deletes one or more data streams and their backing indices.
+        .. raw:: html
+
+          <p>Delete data streams.
+          Deletes one or more data streams and their backing indices.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -1027,10 +1060,13 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Delete an index template. The provided <index-template> may contain multiple
-        template names separated by a comma. If multiple template names are specified
-        then there is no wildcard support and the provided names should match completely
-        with existing templates.
+        .. raw:: html
+
+          <p>Delete an index template.
+          The provided <!-- raw HTML omitted --> may contain multiple template names separated by a comma. If multiple template
+          names are specified then there is no wildcard support and the provided names should match completely with
+          existing templates.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-delete-template.html>`_
 
@@ -1082,7 +1118,10 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Delete a legacy index template.
+        .. raw:: html
+
+          <p>Delete a legacy index template.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-delete-template-v1.html>`_
 
@@ -1145,16 +1184,16 @@ class IndicesClient(NamespacedClient):
         run_expensive_tasks: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Analyze the index disk usage. Analyze the disk usage of each field of an index
-        or data stream. This API might not support indices created in previous Elasticsearch
-        versions. The result of a small index can be inaccurate as some parts of an index
-        might not be analyzed by the API. NOTE: The total size of fields of the analyzed
-        shards of the index in the response is usually smaller than the index `store_size`
-        value because some small metadata files are ignored and some parts of data files
-        might not be scanned by the API. Since stored fields are stored together in a
-        compressed format, the sizes of stored fields are also estimates and can be inaccurate.
-        The stored size of the `_id` field is likely underestimated while the `_source`
-        field is overestimated.
+        .. raw:: html
+
+          <p>Analyze the index disk usage.
+          Analyze the disk usage of each field of an index or data stream.
+          This API might not support indices created in previous Elasticsearch versions.
+          The result of a small index can be inaccurate as some parts of an index might not be analyzed by the API.</p>
+          <p>NOTE: The total size of fields of the analyzed shards of the index in the response is usually smaller than the index <code>store_size</code> value because some small metadata files are ignored and some parts of data files might not be scanned by the API.
+          Since stored fields are stored together in a compressed format, the sizes of stored fields are also estimates and can be inaccurate.
+          The stored size of the <code>_id</code> field is likely underestimated while the <code>_source</code> field is overestimated.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-disk-usage.html>`_
 
@@ -1228,14 +1267,16 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Downsample an index. Aggregate a time series (TSDS) index and store pre-computed
-        statistical summaries (`min`, `max`, `sum`, `value_count` and `avg`) for each
-        metric field grouped by a configured time interval. For example, a TSDS index
-        that contains metrics sampled every 10 seconds can be downsampled to an hourly
-        index. All documents within an hour interval are summarized and stored as a single
-        document in the downsample index. NOTE: Only indices in a time series data stream
-        are supported. Neither field nor document level security can be defined on the
-        source index. The source index must be read only (`index.blocks.write: true`).
+        .. raw:: html
+
+          <p>Downsample an index.
+          Aggregate a time series (TSDS) index and store pre-computed statistical summaries (<code>min</code>, <code>max</code>, <code>sum</code>, <code>value_count</code> and <code>avg</code>) for each metric field grouped by a configured time interval.
+          For example, a TSDS index that contains metrics sampled every 10 seconds can be downsampled to an hourly index.
+          All documents within an hour interval are summarized and stored as a single document in the downsample index.</p>
+          <p>NOTE: Only indices in a time series data stream are supported.
+          Neither field nor document level security can be defined on the source index.
+          The source index must be read only (<code>index.blocks.write: true</code>).</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-downsample-data-stream.html>`_
 
@@ -1303,7 +1344,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> HeadApiResponse:
         """
-        Check indices. Check if one or more indices, index aliases, or data streams exist.
+        .. raw:: html
+
+          <p>Check indices.
+          Check if one or more indices, index aliases, or data streams exist.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-exists.html>`_
 
@@ -1381,7 +1426,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> HeadApiResponse:
         """
-        Check aliases. Checks if one or more data stream or index aliases exist.
+        .. raw:: html
+
+          <p>Check aliases.
+          Checks if one or more data stream or index aliases exist.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-aliases.html>`_
 
@@ -1451,7 +1500,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> HeadApiResponse:
         """
-        Check index templates. Check whether index templates exist.
+        .. raw:: html
+
+          <p>Check index templates.
+          Check whether index templates exist.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/index-templates.html>`_
 
@@ -1500,11 +1553,13 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> HeadApiResponse:
         """
-        Check existence of index templates. Get information about whether index templates
-        exist. Index templates define settings, mappings, and aliases that can be applied
-        automatically to new indices. IMPORTANT: This documentation is about legacy index
-        templates, which are deprecated and will be replaced by the composable templates
-        introduced in Elasticsearch 7.8.
+        .. raw:: html
+
+          <p>Check existence of index templates.
+          Get information about whether index templates exist.
+          Index templates define settings, mappings, and aliases that can be applied automatically to new indices.</p>
+          <p>IMPORTANT: This documentation is about legacy index templates, which are deprecated and will be replaced by the composable templates introduced in Elasticsearch 7.8.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-template-exists-v1.html>`_
 
@@ -1558,10 +1613,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get the status for a data stream lifecycle. Get information about an index or
-        data stream's current data stream lifecycle status, such as time since index
-        creation, time since rollover, the lifecycle configuration managing the index,
-        or any errors encountered during lifecycle execution.
+        .. raw:: html
+
+          <p>Get the status for a data stream lifecycle.
+          Get information about an index or data stream's current data stream lifecycle status, such as time since index creation, time since rollover, the lifecycle configuration managing the index, or any errors encountered during lifecycle execution.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams-explain-lifecycle.html>`_
 
@@ -1625,13 +1681,15 @@ class IndicesClient(NamespacedClient):
         ] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get field usage stats. Get field usage information for each shard and field of
-        an index. Field usage statistics are automatically captured when queries are
-        running on a cluster. A shard-level search request that accesses a given field,
-        even if multiple times during that request, is counted as a single use. The response
-        body reports the per-shard usage count of the data structures that back the fields
-        in the index. A given request will increment each count by a maximum value of
-        1, even if the request accesses the same field multiple times.
+        .. raw:: html
+
+          <p>Get field usage stats.
+          Get field usage information for each shard and field of an index.
+          Field usage statistics are automatically captured when queries are running on a cluster.
+          A shard-level search request that accesses a given field, even if multiple times during that request, is counted as a single use.</p>
+          <p>The response body reports the per-shard usage count of the data structures that back the fields in the index.
+          A given request will increment each count by a maximum value of 1, even if the request accesses the same field multiple times.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/field-usage-stats.html>`_
 
@@ -1719,22 +1777,18 @@ class IndicesClient(NamespacedClient):
         wait_if_ongoing: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Flush data streams or indices. Flushing a data stream or index is the process
-        of making sure that any data that is currently only stored in the transaction
-        log is also permanently stored in the Lucene index. When restarting, Elasticsearch
-        replays any unflushed operations from the transaction log into the Lucene index
-        to bring it back into the state that it was in before the restart. Elasticsearch
-        automatically triggers flushes as needed, using heuristics that trade off the
-        size of the unflushed transaction log against the cost of performing each flush.
-        After each operation has been flushed it is permanently stored in the Lucene
-        index. This may mean that there is no need to maintain an additional copy of
-        it in the transaction log. The transaction log is made up of multiple files,
-        called generations, and Elasticsearch will delete any generation files when they
-        are no longer needed, freeing up disk space. It is also possible to trigger a
-        flush on one or more indices using the flush API, although it is rare for users
-        to need to call this API directly. If you call the flush API after indexing some
-        documents then a successful response indicates that Elasticsearch has flushed
-        all the documents that were indexed before the flush API was called.
+        .. raw:: html
+
+          <p>Flush data streams or indices.
+          Flushing a data stream or index is the process of making sure that any data that is currently only stored in the transaction log is also permanently stored in the Lucene index.
+          When restarting, Elasticsearch replays any unflushed operations from the transaction log into the Lucene index to bring it back into the state that it was in before the restart.
+          Elasticsearch automatically triggers flushes as needed, using heuristics that trade off the size of the unflushed transaction log against the cost of performing each flush.</p>
+          <p>After each operation has been flushed it is permanently stored in the Lucene index.
+          This may mean that there is no need to maintain an additional copy of it in the transaction log.
+          The transaction log is made up of multiple files, called generations, and Elasticsearch will delete any generation files when they are no longer needed, freeing up disk space.</p>
+          <p>It is also possible to trigger a flush on one or more indices using the flush API, although it is rare for users to need to call this API directly.
+          If you call the flush API after indexing some documents then a successful response indicates that Elasticsearch has flushed all the documents that were indexed before the flush API was called.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-flush.html>`_
 
@@ -1817,49 +1871,49 @@ class IndicesClient(NamespacedClient):
         wait_for_completion: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Force a merge. Perform the force merge operation on the shards of one or more
-        indices. For data streams, the API forces a merge on the shards of the stream's
-        backing indices. Merging reduces the number of segments in each shard by merging
-        some of them together and also frees up the space used by deleted documents.
-        Merging normally happens automatically, but sometimes it is useful to trigger
-        a merge manually. WARNING: We recommend force merging only a read-only index
-        (meaning the index is no longer receiving writes). When documents are updated
-        or deleted, the old version is not immediately removed but instead soft-deleted
-        and marked with a "tombstone". These soft-deleted documents are automatically
-        cleaned up during regular segment merges. But force merge can cause very large
-        (greater than 5 GB) segments to be produced, which are not eligible for regular
-        merges. So the number of soft-deleted documents can then grow rapidly, resulting
-        in higher disk usage and worse search performance. If you regularly force merge
-        an index receiving writes, this can also make snapshots more expensive, since
-        the new documents can't be backed up incrementally. **Blocks during a force merge**
-        Calls to this API block until the merge is complete (unless request contains
-        `wait_for_completion=false`). If the client connection is lost before completion
-        then the force merge process will continue in the background. Any new requests
-        to force merge the same indices will also block until the ongoing force merge
-        is complete. **Running force merge asynchronously** If the request contains `wait_for_completion=false`,
-        Elasticsearch performs some preflight checks, launches the request, and returns
-        a task you can use to get the status of the task. However, you can not cancel
-        this task as the force merge task is not cancelable. Elasticsearch creates a
-        record of this task as a document at `_tasks/<task_id>`. When you are done with
-        a task, you should delete the task document so Elasticsearch can reclaim the
-        space. **Force merging multiple indices** You can force merge multiple indices
-        with a single request by targeting: * One or more data streams that contain multiple
-        backing indices * Multiple indices * One or more aliases * All data streams and
-        indices in a cluster Each targeted shard is force-merged separately using the
-        force_merge threadpool. By default each node only has a single `force_merge`
-        thread which means that the shards on that node are force-merged one at a time.
-        If you expand the `force_merge` threadpool on a node then it will force merge
-        its shards in parallel Force merge makes the storage for the shard being merged
-        temporarily increase, as it may require free space up to triple its size in case
-        `max_num_segments parameter` is set to `1`, to rewrite all segments into a new
-        one. **Data streams and time-based indices** Force-merging is useful for managing
-        a data stream's older backing indices and other time-based indices, particularly
-        after a rollover. In these cases, each index only receives indexing traffic for
-        a certain period of time. Once an index receive no more writes, its shards can
-        be force-merged to a single segment. This can be a good idea because single-segment
-        shards can sometimes use simpler and more efficient data structures to perform
-        searches. For example: ``` POST /.ds-my-data-stream-2099.03.07-000001/_forcemerge?max_num_segments=1
-        ```
+        .. raw:: html
+
+          <p>Force a merge.
+          Perform the force merge operation on the shards of one or more indices.
+          For data streams, the API forces a merge on the shards of the stream's backing indices.</p>
+          <p>Merging reduces the number of segments in each shard by merging some of them together and also frees up the space used by deleted documents.
+          Merging normally happens automatically, but sometimes it is useful to trigger a merge manually.</p>
+          <p>WARNING: We recommend force merging only a read-only index (meaning the index is no longer receiving writes).
+          When documents are updated or deleted, the old version is not immediately removed but instead soft-deleted and marked with a &quot;tombstone&quot;.
+          These soft-deleted documents are automatically cleaned up during regular segment merges.
+          But force merge can cause very large (greater than 5 GB) segments to be produced, which are not eligible for regular merges.
+          So the number of soft-deleted documents can then grow rapidly, resulting in higher disk usage and worse search performance.
+          If you regularly force merge an index receiving writes, this can also make snapshots more expensive, since the new documents can't be backed up incrementally.</p>
+          <p><strong>Blocks during a force merge</strong></p>
+          <p>Calls to this API block until the merge is complete (unless request contains <code>wait_for_completion=false</code>).
+          If the client connection is lost before completion then the force merge process will continue in the background.
+          Any new requests to force merge the same indices will also block until the ongoing force merge is complete.</p>
+          <p><strong>Running force merge asynchronously</strong></p>
+          <p>If the request contains <code>wait_for_completion=false</code>, Elasticsearch performs some preflight checks, launches the request, and returns a task you can use to get the status of the task.
+          However, you can not cancel this task as the force merge task is not cancelable.
+          Elasticsearch creates a record of this task as a document at <code>_tasks/&lt;task_id&gt;</code>.
+          When you are done with a task, you should delete the task document so Elasticsearch can reclaim the space.</p>
+          <p><strong>Force merging multiple indices</strong></p>
+          <p>You can force merge multiple indices with a single request by targeting:</p>
+          <ul>
+          <li>One or more data streams that contain multiple backing indices</li>
+          <li>Multiple indices</li>
+          <li>One or more aliases</li>
+          <li>All data streams and indices in a cluster</li>
+          </ul>
+          <p>Each targeted shard is force-merged separately using the force_merge threadpool.
+          By default each node only has a single <code>force_merge</code> thread which means that the shards on that node are force-merged one at a time.
+          If you expand the <code>force_merge</code> threadpool on a node then it will force merge its shards in parallel</p>
+          <p>Force merge makes the storage for the shard being merged temporarily increase, as it may require free space up to triple its size in case <code>max_num_segments parameter</code> is set to <code>1</code>, to rewrite all segments into a new one.</p>
+          <p><strong>Data streams and time-based indices</strong></p>
+          <p>Force-merging is useful for managing a data stream's older backing indices and other time-based indices, particularly after a rollover.
+          In these cases, each index only receives indexing traffic for a certain period of time.
+          Once an index receive no more writes, its shards can be force-merged to a single segment.
+          This can be a good idea because single-segment shards can sometimes use simpler and more efficient data structures to perform searches.
+          For example:</p>
+          <pre><code>POST /.ds-my-data-stream-2099.03.07-000001/_forcemerge?max_num_segments=1
+          </code></pre>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-forcemerge.html>`_
 
@@ -1952,8 +2006,12 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index information. Get information about one or more indices. For data streams,
-        the API returns information about the stream’s backing indices.
+        .. raw:: html
+
+          <p>Get index information.
+          Get information about one or more indices. For data streams, the API returns information about the
+          stream’s backing indices.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-index.html>`_
 
@@ -2042,7 +2100,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get aliases. Retrieves information for one or more data stream or index aliases.
+        .. raw:: html
+
+          <p>Get aliases.
+          Retrieves information for one or more data stream or index aliases.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-alias.html>`_
 
@@ -2124,8 +2186,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get data stream lifecycles. Retrieves the data stream lifecycle configuration
-        of one or more data streams.
+        .. raw:: html
+
+          <p>Get data stream lifecycles.
+          Retrieves the data stream lifecycle configuration of one or more data streams.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams-get-lifecycle.html>`_
 
@@ -2179,8 +2244,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get data stream lifecycle stats. Get statistics about the data streams that are
-        managed by a data stream lifecycle.
+        .. raw:: html
+
+          <p>Get data stream lifecycle stats.
+          Get statistics about the data streams that are managed by a data stream lifecycle.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams-get-lifecycle-stats.html>`_
         """
@@ -2227,7 +2295,11 @@ class IndicesClient(NamespacedClient):
         verbose: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get data streams. Retrieves information about one or more data streams.
+        .. raw:: html
+
+          <p>Get data streams.
+          Retrieves information about one or more data streams.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -2302,10 +2374,13 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get mapping definitions. Retrieves mapping definitions for one or more fields.
-        For data streams, the API retrieves field mappings for the stream’s backing indices.
-        This API is useful if you don't need a complete mapping or if an index mapping
-        contains a large number of fields.
+        .. raw:: html
+
+          <p>Get mapping definitions.
+          Retrieves mapping definitions for one or more fields.
+          For data streams, the API retrieves field mappings for the stream’s backing indices.</p>
+          <p>This API is useful if you don't need a complete mapping or if an index mapping contains a large number of fields.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-field-mapping.html>`_
 
@@ -2382,7 +2457,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index templates. Get information about one or more index templates.
+        .. raw:: html
+
+          <p>Get index templates.
+          Get information about one or more index templates.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-template.html>`_
 
@@ -2455,8 +2534,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get mapping definitions. For data streams, the API retrieves mappings for the
-        stream’s backing indices.
+        .. raw:: html
+
+          <p>Get mapping definitions.
+          For data streams, the API retrieves mappings for the stream’s backing indices.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-mapping.html>`_
 
@@ -2540,8 +2622,12 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index settings. Get setting information for one or more indices. For data
-        streams, it returns setting information for the stream's backing indices.
+        .. raw:: html
+
+          <p>Get index settings.
+          Get setting information for one or more indices.
+          For data streams, it returns setting information for the stream's backing indices.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-settings.html>`_
 
@@ -2628,9 +2714,12 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index templates. Get information about one or more index templates. IMPORTANT:
-        This documentation is about legacy index templates, which are deprecated and
-        will be replaced by the composable templates introduced in Elasticsearch 7.8.
+        .. raw:: html
+
+          <p>Get index templates.
+          Get information about one or more index templates.</p>
+          <p>IMPORTANT: This documentation is about legacy index templates, which are deprecated and will be replaced by the composable templates introduced in Elasticsearch 7.8.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-get-template-v1.html>`_
 
@@ -2689,14 +2778,20 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Convert an index alias to a data stream. Converts an index alias to a data stream.
-        You must have a matching index template that is data stream enabled. The alias
-        must meet the following criteria: The alias must have a write index; All indices
-        for the alias must have a `@timestamp` field mapping of a `date` or `date_nanos`
-        field type; The alias must not have any filters; The alias must not use custom
-        routing. If successful, the request removes the alias and creates a data stream
-        with the same name. The indices for the alias become hidden backing indices for
-        the stream. The write index for the alias becomes the write index for the stream.
+        .. raw:: html
+
+          <p>Convert an index alias to a data stream.
+          Converts an index alias to a data stream.
+          You must have a matching index template that is data stream enabled.
+          The alias must meet the following criteria:
+          The alias must have a write index;
+          All indices for the alias must have a <code>@timestamp</code> field mapping of a <code>date</code> or <code>date_nanos</code> field type;
+          The alias must not have any filters;
+          The alias must not use custom routing.
+          If successful, the request removes the alias and creates a data stream with the same name.
+          The indices for the alias become hidden backing indices for the stream.
+          The write index for the alias becomes the write index for the stream.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -2748,8 +2843,11 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Update data streams. Performs one or more data stream modification actions in
-        a single atomic operation.
+        .. raw:: html
+
+          <p>Update data streams.
+          Performs one or more data stream modification actions in a single atomic operation.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -2809,27 +2907,26 @@ class IndicesClient(NamespacedClient):
         ] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Open a closed index. For data streams, the API opens any closed backing indices.
-        A closed index is blocked for read/write operations and does not allow all operations
-        that opened indices allow. It is not possible to index documents or to search
-        for documents in a closed index. This allows closed indices to not have to maintain
-        internal data structures for indexing or searching documents, resulting in a
-        smaller overhead on the cluster. When opening or closing an index, the master
-        is responsible for restarting the index shards to reflect the new state of the
-        index. The shards will then go through the normal recovery process. The data
-        of opened or closed indices is automatically replicated by the cluster to ensure
-        that enough shard copies are safely kept around at all times. You can open and
-        close multiple indices. An error is thrown if the request explicitly refers to
-        a missing index. This behavior can be turned off by using the `ignore_unavailable=true`
-        parameter. By default, you must explicitly name the indices you are opening or
-        closing. To open or close indices with `_all`, `*`, or other wildcard expressions,
-        change the `action.destructive_requires_name` setting to `false`. This setting
-        can also be changed with the cluster update settings API. Closed indices consume
-        a significant amount of disk-space which can cause problems in managed environments.
-        Closing indices can be turned off with the cluster settings API by setting `cluster.indices.close.enable`
-        to `false`. Because opening or closing an index allocates its shards, the `wait_for_active_shards`
-        setting on index creation applies to the `_open` and `_close` index actions as
-        well.
+        .. raw:: html
+
+          <p>Open a closed index.
+          For data streams, the API opens any closed backing indices.</p>
+          <p>A closed index is blocked for read/write operations and does not allow all operations that opened indices allow.
+          It is not possible to index documents or to search for documents in a closed index.
+          This allows closed indices to not have to maintain internal data structures for indexing or searching documents, resulting in a smaller overhead on the cluster.</p>
+          <p>When opening or closing an index, the master is responsible for restarting the index shards to reflect the new state of the index.
+          The shards will then go through the normal recovery process.
+          The data of opened or closed indices is automatically replicated by the cluster to ensure that enough shard copies are safely kept around at all times.</p>
+          <p>You can open and close multiple indices.
+          An error is thrown if the request explicitly refers to a missing index.
+          This behavior can be turned off by using the <code>ignore_unavailable=true</code> parameter.</p>
+          <p>By default, you must explicitly name the indices you are opening or closing.
+          To open or close indices with <code>_all</code>, <code>*</code>, or other wildcard expressions, change the <code>action.destructive_requires_name</code> setting to <code>false</code>.
+          This setting can also be changed with the cluster update settings API.</p>
+          <p>Closed indices consume a significant amount of disk-space which can cause problems in managed environments.
+          Closing indices can be turned off with the cluster settings API by setting <code>cluster.indices.close.enable</code> to <code>false</code>.</p>
+          <p>Because opening or closing an index allocates its shards, the <code>wait_for_active_shards</code> setting on index creation applies to the <code>_open</code> and <code>_close</code> index actions as well.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-open-close.html>`_
 
@@ -2904,18 +3001,18 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Promote a data stream. Promote a data stream from a replicated data stream managed
-        by cross-cluster replication (CCR) to a regular data stream. With CCR auto following,
-        a data stream from a remote cluster can be replicated to the local cluster. These
-        data streams can't be rolled over in the local cluster. These replicated data
-        streams roll over only if the upstream data stream rolls over. In the event that
-        the remote cluster is no longer available, the data stream in the local cluster
-        can be promoted to a regular data stream, which allows these data streams to
-        be rolled over in the local cluster. NOTE: When promoting a data stream, ensure
-        the local cluster has a data stream enabled index template that matches the data
-        stream. If this is missing, the data stream will not be able to roll over until
-        a matching index template is created. This will affect the lifecycle management
-        of the data stream and interfere with the data stream size and retention.
+        .. raw:: html
+
+          <p>Promote a data stream.
+          Promote a data stream from a replicated data stream managed by cross-cluster replication (CCR) to a regular data stream.</p>
+          <p>With CCR auto following, a data stream from a remote cluster can be replicated to the local cluster.
+          These data streams can't be rolled over in the local cluster.
+          These replicated data streams roll over only if the upstream data stream rolls over.
+          In the event that the remote cluster is no longer available, the data stream in the local cluster can be promoted to a regular data stream, which allows these data streams to be rolled over in the local cluster.</p>
+          <p>NOTE: When promoting a data stream, ensure the local cluster has a data stream enabled index template that matches the data stream.
+          If this is missing, the data stream will not be able to roll over until a matching index template is created.
+          This will affect the lifecycle management of the data stream and interfere with the data stream size and retention.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams.html>`_
 
@@ -2977,7 +3074,11 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Create or update an alias. Adds a data stream or index to an alias.
+        .. raw:: html
+
+          <p>Create or update an alias.
+          Adds a data stream or index to an alias.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-aliases.html>`_
 
@@ -3079,8 +3180,11 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Update data stream lifecycles. Update the data stream lifecycle of the specified
-        data streams.
+        .. raw:: html
+
+          <p>Update data stream lifecycles.
+          Update the data stream lifecycle of the specified data streams.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/data-streams-put-lifecycle.html>`_
 
@@ -3181,34 +3285,30 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Create or update an index template. Index templates define settings, mappings,
-        and aliases that can be applied automatically to new indices. Elasticsearch applies
-        templates to new indices based on an wildcard pattern that matches the index
-        name. Index templates are applied during data stream or index creation. For data
-        streams, these settings and mappings are applied when the stream's backing indices
-        are created. Settings and mappings specified in a create index API request override
-        any settings or mappings specified in an index template. Changes to index templates
-        do not affect existing indices, including the existing backing indices of a data
-        stream. You can use C-style `/* *\\/` block comments in index templates. You
-        can include comments anywhere in the request body, except before the opening
-        curly bracket. **Multiple matching templates** If multiple index templates match
-        the name of a new index or data stream, the template with the highest priority
-        is used. Multiple templates with overlapping index patterns at the same priority
-        are not allowed and an error will be thrown when attempting to create a template
-        matching an existing index template at identical priorities. **Composing aliases,
-        mappings, and settings** When multiple component templates are specified in the
-        `composed_of` field for an index template, they are merged in the order specified,
-        meaning that later component templates override earlier component templates.
-        Any mappings, settings, or aliases from the parent index template are merged
-        in next. Finally, any configuration on the index request itself is merged. Mapping
-        definitions are merged recursively, which means that later mapping components
-        can introduce new field mappings and update the mapping configuration. If a field
-        mapping is already contained in an earlier component, its definition will be
-        completely overwritten by the later one. This recursive merging strategy applies
-        not only to field mappings, but also root options like `dynamic_templates` and
-        `meta`. If an earlier component contains a `dynamic_templates` block, then by
-        default new `dynamic_templates` entries are appended onto the end. If an entry
-        already exists with the same key, then it is overwritten by the new definition.
+        .. raw:: html
+
+          <p>Create or update an index template.
+          Index templates define settings, mappings, and aliases that can be applied automatically to new indices.</p>
+          <p>Elasticsearch applies templates to new indices based on an wildcard pattern that matches the index name.
+          Index templates are applied during data stream or index creation.
+          For data streams, these settings and mappings are applied when the stream's backing indices are created.
+          Settings and mappings specified in a create index API request override any settings or mappings specified in an index template.
+          Changes to index templates do not affect existing indices, including the existing backing indices of a data stream.</p>
+          <p>You can use C-style <code>/* *\\/</code> block comments in index templates.
+          You can include comments anywhere in the request body, except before the opening curly bracket.</p>
+          <p><strong>Multiple matching templates</strong></p>
+          <p>If multiple index templates match the name of a new index or data stream, the template with the highest priority is used.</p>
+          <p>Multiple templates with overlapping index patterns at the same priority are not allowed and an error will be thrown when attempting to create a template matching an existing index template at identical priorities.</p>
+          <p><strong>Composing aliases, mappings, and settings</strong></p>
+          <p>When multiple component templates are specified in the <code>composed_of</code> field for an index template, they are merged in the order specified, meaning that later component templates override earlier component templates.
+          Any mappings, settings, or aliases from the parent index template are merged in next.
+          Finally, any configuration on the index request itself is merged.
+          Mapping definitions are merged recursively, which means that later mapping components can introduce new field mappings and update the mapping configuration.
+          If a field mapping is already contained in an earlier component, its definition will be completely overwritten by the later one.
+          This recursive merging strategy applies not only to field mappings, but also root options like <code>dynamic_templates</code> and <code>meta</code>.
+          If an earlier component contains a <code>dynamic_templates</code> block, then by default new <code>dynamic_templates</code> entries are appended onto the end.
+          If an entry already exists with the same key, then it is overwritten by the new definition.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-put-template.html>`_
 
@@ -3341,10 +3441,7 @@ class IndicesClient(NamespacedClient):
         ] = None,
         dynamic_date_formats: t.Optional[t.Sequence[str]] = None,
         dynamic_templates: t.Optional[
-            t.Union[
-                t.Mapping[str, t.Mapping[str, t.Any]],
-                t.Sequence[t.Mapping[str, t.Mapping[str, t.Any]]],
-            ]
+            t.Sequence[t.Mapping[str, t.Mapping[str, t.Any]]]
         ] = None,
         error_trace: t.Optional[bool] = None,
         expand_wildcards: t.Optional[
@@ -3372,27 +3469,29 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Update field mappings. Add new fields to an existing data stream or index. You
-        can also use this API to change the search settings of existing fields and add
-        new properties to existing object fields. For data streams, these changes are
-        applied to all backing indices by default. **Add multi-fields to an existing
-        field** Multi-fields let you index the same field in different ways. You can
-        use this API to update the fields mapping parameter and enable multi-fields for
-        an existing field. WARNING: If an index (or data stream) contains documents when
-        you add a multi-field, those documents will not have values for the new multi-field.
-        You can populate the new multi-field with the update by query API. **Change supported
-        mapping parameters for an existing field** The documentation for each mapping
-        parameter indicates whether you can update it for an existing field using this
-        API. For example, you can use the update mapping API to update the `ignore_above`
-        parameter. **Change the mapping of an existing field** Except for supported mapping
-        parameters, you can't change the mapping or field type of an existing field.
-        Changing an existing field could invalidate data that's already indexed. If you
-        need to change the mapping of a field in a data stream's backing indices, refer
-        to documentation about modifying data streams. If you need to change the mapping
-        of a field in other indices, create a new index with the correct mapping and
-        reindex your data into that index. **Rename a field** Renaming a field would
-        invalidate data already indexed under the old field name. Instead, add an alias
-        field to create an alternate field name.
+        .. raw:: html
+
+          <p>Update field mappings.
+          Add new fields to an existing data stream or index.
+          You can also use this API to change the search settings of existing fields and add new properties to existing object fields.
+          For data streams, these changes are applied to all backing indices by default.</p>
+          <p><strong>Add multi-fields to an existing field</strong></p>
+          <p>Multi-fields let you index the same field in different ways.
+          You can use this API to update the fields mapping parameter and enable multi-fields for an existing field.
+          WARNING: If an index (or data stream) contains documents when you add a multi-field, those documents will not have values for the new multi-field.
+          You can populate the new multi-field with the update by query API.</p>
+          <p><strong>Change supported mapping parameters for an existing field</strong></p>
+          <p>The documentation for each mapping parameter indicates whether you can update it for an existing field using this API.
+          For example, you can use the update mapping API to update the <code>ignore_above</code> parameter.</p>
+          <p><strong>Change the mapping of an existing field</strong></p>
+          <p>Except for supported mapping parameters, you can't change the mapping or field type of an existing field.
+          Changing an existing field could invalidate data that's already indexed.</p>
+          <p>If you need to change the mapping of a field in a data stream's backing indices, refer to documentation about modifying data streams.
+          If you need to change the mapping of a field in other indices, create a new index with the correct mapping and reindex your data into that index.</p>
+          <p><strong>Rename a field</strong></p>
+          <p>Renaming a field would invalidate data already indexed under the old field name.
+          Instead, add an alias field to create an alternate field name.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-put-mapping.html>`_
 
@@ -3521,21 +3620,23 @@ class IndicesClient(NamespacedClient):
         timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Update index settings. Changes dynamic index settings in real time. For data
-        streams, index setting changes are applied to all backing indices by default.
-        To revert a setting to the default value, use a null value. The list of per-index
-        settings that can be updated dynamically on live indices can be found in index
-        module documentation. To preserve existing settings from being updated, set the
-        `preserve_existing` parameter to `true`. NOTE: You can only define new analyzers
-        on closed indices. To add an analyzer, you must close the index, define the analyzer,
-        and reopen the index. You cannot close the write index of a data stream. To update
-        the analyzer for a data stream's write index and future backing indices, update
-        the analyzer in the index template used by the stream. Then roll over the data
-        stream to apply the new analyzer to the stream's write index and future backing
-        indices. This affects searches and any new data added to the stream after the
-        rollover. However, it does not affect the data stream's backing indices or their
-        existing data. To change the analyzer for existing backing indices, you must
-        create a new data stream and reindex your data into it.
+        .. raw:: html
+
+          <p>Update index settings.
+          Changes dynamic index settings in real time.
+          For data streams, index setting changes are applied to all backing indices by default.</p>
+          <p>To revert a setting to the default value, use a null value.
+          The list of per-index settings that can be updated dynamically on live indices can be found in index module documentation.
+          To preserve existing settings from being updated, set the <code>preserve_existing</code> parameter to <code>true</code>.</p>
+          <p>NOTE: You can only define new analyzers on closed indices.
+          To add an analyzer, you must close the index, define the analyzer, and reopen the index.
+          You cannot close the write index of a data stream.
+          To update the analyzer for a data stream's write index and future backing indices, update the analyzer in the index template used by the stream.
+          Then roll over the data stream to apply the new analyzer to the stream's write index and future backing indices.
+          This affects searches and any new data added to the stream after the rollover.
+          However, it does not affect the data stream's backing indices or their existing data.
+          To change the analyzer for existing backing indices, you must create a new data stream and reindex your data into it.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-update-settings.html>`_
 
@@ -3639,24 +3740,24 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Create or update an index template. Index templates define settings, mappings,
-        and aliases that can be applied automatically to new indices. Elasticsearch applies
-        templates to new indices based on an index pattern that matches the index name.
-        IMPORTANT: This documentation is about legacy index templates, which are deprecated
-        and will be replaced by the composable templates introduced in Elasticsearch
-        7.8. Composable templates always take precedence over legacy templates. If no
-        composable template matches a new index, matching legacy templates are applied
-        according to their order. Index templates are only applied during index creation.
-        Changes to index templates do not affect existing indices. Settings and mappings
-        specified in create index API requests override any settings or mappings specified
-        in an index template. You can use C-style `/* *\\/` block comments in index templates.
-        You can include comments anywhere in the request body, except before the opening
-        curly bracket. **Indices matching multiple templates** Multiple index templates
-        can potentially match an index, in this case, both the settings and mappings
-        are merged into the final configuration of the index. The order of the merging
-        can be controlled using the order parameter, with lower order being applied first,
-        and higher orders overriding them. NOTE: Multiple matching templates with the
-        same order value will result in a non-deterministic merging order.
+        .. raw:: html
+
+          <p>Create or update an index template.
+          Index templates define settings, mappings, and aliases that can be applied automatically to new indices.
+          Elasticsearch applies templates to new indices based on an index pattern that matches the index name.</p>
+          <p>IMPORTANT: This documentation is about legacy index templates, which are deprecated and will be replaced by the composable templates introduced in Elasticsearch 7.8.</p>
+          <p>Composable templates always take precedence over legacy templates.
+          If no composable template matches a new index, matching legacy templates are applied according to their order.</p>
+          <p>Index templates are only applied during index creation.
+          Changes to index templates do not affect existing indices.
+          Settings and mappings specified in create index API requests override any settings or mappings specified in an index template.</p>
+          <p>You can use C-style <code>/* *\\/</code> block comments in index templates.
+          You can include comments anywhere in the request body, except before the opening curly bracket.</p>
+          <p><strong>Indices matching multiple templates</strong></p>
+          <p>Multiple index templates can potentially match an index, in this case, both the settings and mappings are merged into the final configuration of the index.
+          The order of the merging can be controlled using the order parameter, with lower order being applied first, and higher orders overriding them.
+          NOTE: Multiple matching templates with the same order value will result in a non-deterministic merging order.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-templates-v1.html>`_
 
@@ -3737,27 +3838,28 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index recovery information. Get information about ongoing and completed shard
-        recoveries for one or more indices. For data streams, the API returns information
-        for the stream's backing indices. All recoveries, whether ongoing or complete,
-        are kept in the cluster state and may be reported on at any time. Shard recovery
-        is the process of initializing a shard copy, such as restoring a primary shard
-        from a snapshot or creating a replica shard from a primary shard. When a shard
-        recovery completes, the recovered shard is available for search and indexing.
-        Recovery automatically occurs during the following processes: * When creating
-        an index for the first time. * When a node rejoins the cluster and starts up
-        any missing primary shard copies using the data that it holds in its data path.
-        * Creation of new replica shard copies from the primary. * Relocation of a shard
-        copy to a different node in the same cluster. * A snapshot restore operation.
-        * A clone, shrink, or split operation. You can determine the cause of a shard
-        recovery using the recovery or cat recovery APIs. The index recovery API reports
-        information about completed recoveries only for shard copies that currently exist
-        in the cluster. It only reports the last recovery for each shard copy and does
-        not report historical information about earlier recoveries, nor does it report
-        information about the recoveries of shard copies that no longer exist. This means
-        that if a shard copy completes a recovery and then Elasticsearch relocates it
-        onto a different node then the information about the original recovery will not
-        be shown in the recovery API.
+        .. raw:: html
+
+          <p>Get index recovery information.
+          Get information about ongoing and completed shard recoveries for one or more indices.
+          For data streams, the API returns information for the stream's backing indices.</p>
+          <p>All recoveries, whether ongoing or complete, are kept in the cluster state and may be reported on at any time.</p>
+          <p>Shard recovery is the process of initializing a shard copy, such as restoring a primary shard from a snapshot or creating a replica shard from a primary shard.
+          When a shard recovery completes, the recovered shard is available for search and indexing.</p>
+          <p>Recovery automatically occurs during the following processes:</p>
+          <ul>
+          <li>When creating an index for the first time.</li>
+          <li>When a node rejoins the cluster and starts up any missing primary shard copies using the data that it holds in its data path.</li>
+          <li>Creation of new replica shard copies from the primary.</li>
+          <li>Relocation of a shard copy to a different node in the same cluster.</li>
+          <li>A snapshot restore operation.</li>
+          <li>A clone, shrink, or split operation.</li>
+          </ul>
+          <p>You can determine the cause of a shard recovery using the recovery or cat recovery APIs.</p>
+          <p>The index recovery API reports information about completed recoveries only for shard copies that currently exist in the cluster.
+          It only reports the last recovery for each shard copy and does not report historical information about earlier recoveries, nor does it report information about the recoveries of shard copies that no longer exist.
+          This means that if a shard copy completes a recovery and then Elasticsearch relocates it onto a different node then the information about the original recovery will not be shown in the recovery API.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-recovery.html>`_
 
@@ -3819,19 +3921,19 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Refresh an index. A refresh makes recent operations performed on one or more
-        indices available for search. For data streams, the API runs the refresh operation
-        on the stream’s backing indices. By default, Elasticsearch periodically refreshes
-        indices every second, but only on indices that have received one search request
-        or more in the last 30 seconds. You can change this default interval with the
-        `index.refresh_interval` setting. Refresh requests are synchronous and do not
-        return a response until the refresh operation completes. Refreshes are resource-intensive.
-        To ensure good cluster performance, it's recommended to wait for Elasticsearch's
-        periodic refresh rather than performing an explicit refresh when possible. If
-        your application workflow indexes documents and then runs a search to retrieve
-        the indexed document, it's recommended to use the index API's `refresh=wait_for`
-        query parameter option. This option ensures the indexing operation waits for
-        a periodic refresh before running the search.
+        .. raw:: html
+
+          <p>Refresh an index.
+          A refresh makes recent operations performed on one or more indices available for search.
+          For data streams, the API runs the refresh operation on the stream’s backing indices.</p>
+          <p>By default, Elasticsearch periodically refreshes indices every second, but only on indices that have received one search request or more in the last 30 seconds.
+          You can change this default interval with the <code>index.refresh_interval</code> setting.</p>
+          <p>Refresh requests are synchronous and do not return a response until the refresh operation completes.</p>
+          <p>Refreshes are resource-intensive.
+          To ensure good cluster performance, it's recommended to wait for Elasticsearch's periodic refresh rather than performing an explicit refresh when possible.</p>
+          <p>If your application workflow indexes documents and then runs a search to retrieve the indexed document, it's recommended to use the index API's <code>refresh=wait_for</code> query parameter option.
+          This option ensures the indexing operation waits for a periodic refresh before running the search.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-refresh.html>`_
 
@@ -3901,21 +4003,20 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Reload search analyzers. Reload an index's search analyzers and their resources.
-        For data streams, the API reloads search analyzers and resources for the stream's
-        backing indices. IMPORTANT: After reloading the search analyzers you should clear
-        the request cache to make sure it doesn't contain responses derived from the
-        previous versions of the analyzer. You can use the reload search analyzers API
-        to pick up changes to synonym files used in the `synonym_graph` or `synonym`
-        token filter of a search analyzer. To be eligible, the token filter must have
-        an `updateable` flag of `true` and only be used in search analyzers. NOTE: This
-        API does not perform a reload for each shard of an index. Instead, it performs
-        a reload for each node containing index shards. As a result, the total shard
-        count returned by the API can differ from the number of index shards. Because
-        reloading affects every node with an index shard, it is important to update the
-        synonym file on every data node in the cluster--including nodes that don't contain
-        a shard replica--before using this API. This ensures the synonym file is updated
-        everywhere in the cluster in case shards are relocated in the future.
+        .. raw:: html
+
+          <p>Reload search analyzers.
+          Reload an index's search analyzers and their resources.
+          For data streams, the API reloads search analyzers and resources for the stream's backing indices.</p>
+          <p>IMPORTANT: After reloading the search analyzers you should clear the request cache to make sure it doesn't contain responses derived from the previous versions of the analyzer.</p>
+          <p>You can use the reload search analyzers API to pick up changes to synonym files used in the <code>synonym_graph</code> or <code>synonym</code> token filter of a search analyzer.
+          To be eligible, the token filter must have an <code>updateable</code> flag of <code>true</code> and only be used in search analyzers.</p>
+          <p>NOTE: This API does not perform a reload for each shard of an index.
+          Instead, it performs a reload for each node containing index shards.
+          As a result, the total shard count returned by the API can differ from the number of index shards.
+          Because reloading affects every node with an index shard, it is important to update the synonym file on every data node in the cluster--including nodes that don't contain a shard replica--before using this API.
+          This ensures the synonym file is updated everywhere in the cluster in case shards are relocated in the future.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-reload-analyzers.html>`_
 
@@ -3979,38 +4080,33 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Resolve the cluster. Resolve the specified index expressions to return information
-        about each cluster, including the local cluster, if included. Multiple patterns
-        and remote clusters are supported. This endpoint is useful before doing a cross-cluster
-        search in order to determine which remote clusters should be included in a search.
-        You use the same index expression with this endpoint as you would for cross-cluster
-        search. Index and cluster exclusions are also supported with this endpoint. For
-        each cluster in the index expression, information is returned about: * Whether
-        the querying ("local") cluster is currently connected to each remote cluster
-        in the index expression scope. * Whether each remote cluster is configured with
-        `skip_unavailable` as `true` or `false`. * Whether there are any indices, aliases,
-        or data streams on that cluster that match the index expression. * Whether the
-        search is likely to have errors returned when you do the cross-cluster search
-        (including any authorization errors if you do not have permission to query the
-        index). * Cluster version information, including the Elasticsearch server version.
-        For example, `GET /_resolve/cluster/my-index-*,cluster*:my-index-*` returns information
-        about the local cluster and all remotely configured clusters that start with
-        the alias `cluster*`. Each cluster returns information about whether it has any
-        indices, aliases or data streams that match `my-index-*`. **Advantages of using
-        this endpoint before a cross-cluster search** You may want to exclude a cluster
-        or index from a search when: * A remote cluster is not currently connected and
-        is configured with `skip_unavailable=false`. Running a cross-cluster search under
-        those conditions will cause the entire search to fail. * A cluster has no matching
-        indices, aliases or data streams for the index expression (or your user does
-        not have permissions to search them). For example, suppose your index expression
-        is `logs*,remote1:logs*` and the remote1 cluster has no indices, aliases or data
-        streams that match `logs*`. In that case, that cluster will return no results
-        from that cluster if you include it in a cross-cluster search. * The index expression
-        (combined with any query parameters you specify) will likely cause an exception
-        to be thrown when you do the search. In these cases, the "error" field in the
-        `_resolve/cluster` response will be present. (This is also where security/permission
-        errors will be shown.) * A remote cluster is an older version that does not support
-        the feature you want to use in your search.
+        .. raw:: html
+
+          <p>Resolve the cluster.
+          Resolve the specified index expressions to return information about each cluster, including the local cluster, if included.
+          Multiple patterns and remote clusters are supported.</p>
+          <p>This endpoint is useful before doing a cross-cluster search in order to determine which remote clusters should be included in a search.</p>
+          <p>You use the same index expression with this endpoint as you would for cross-cluster search.
+          Index and cluster exclusions are also supported with this endpoint.</p>
+          <p>For each cluster in the index expression, information is returned about:</p>
+          <ul>
+          <li>Whether the querying (&quot;local&quot;) cluster is currently connected to each remote cluster in the index expression scope.</li>
+          <li>Whether each remote cluster is configured with <code>skip_unavailable</code> as <code>true</code> or <code>false</code>.</li>
+          <li>Whether there are any indices, aliases, or data streams on that cluster that match the index expression.</li>
+          <li>Whether the search is likely to have errors returned when you do the cross-cluster search (including any authorization errors if you do not have permission to query the index).</li>
+          <li>Cluster version information, including the Elasticsearch server version.</li>
+          </ul>
+          <p>For example, <code>GET /_resolve/cluster/my-index-*,cluster*:my-index-*</code> returns information about the local cluster and all remotely configured clusters that start with the alias <code>cluster*</code>.
+          Each cluster returns information about whether it has any indices, aliases or data streams that match <code>my-index-*</code>.</p>
+          <p><strong>Advantages of using this endpoint before a cross-cluster search</strong></p>
+          <p>You may want to exclude a cluster or index from a search when:</p>
+          <ul>
+          <li>A remote cluster is not currently connected and is configured with <code>skip_unavailable=false</code>. Running a cross-cluster search under those conditions will cause the entire search to fail.</li>
+          <li>A cluster has no matching indices, aliases or data streams for the index expression (or your user does not have permissions to search them). For example, suppose your index expression is <code>logs*,remote1:logs*</code> and the remote1 cluster has no indices, aliases or data streams that match <code>logs*</code>. In that case, that cluster will return no results from that cluster if you include it in a cross-cluster search.</li>
+          <li>The index expression (combined with any query parameters you specify) will likely cause an exception to be thrown when you do the search. In these cases, the &quot;error&quot; field in the <code>_resolve/cluster</code> response will be present. (This is also where security/permission errors will be shown.)</li>
+          <li>A remote cluster is an older version that does not support the feature you want to use in your search.</li>
+          </ul>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-resolve-cluster-api.html>`_
 
@@ -4083,8 +4179,12 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Resolve indices. Resolve the names and/or index patterns for indices, aliases,
-        and data streams. Multiple patterns and remote clusters are supported.
+        .. raw:: html
+
+          <p>Resolve indices.
+          Resolve the names and/or index patterns for indices, aliases, and data streams.
+          Multiple patterns and remote clusters are supported.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-resolve-index-api.html>`_
 
@@ -4157,33 +4257,35 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Roll over to a new index. TIP: It is recommended to use the index lifecycle rollover
-        action to automate rollovers. The rollover API creates a new index for a data
-        stream or index alias. The API behavior depends on the rollover target. **Roll
-        over a data stream** If you roll over a data stream, the API creates a new write
-        index for the stream. The stream's previous write index becomes a regular backing
-        index. A rollover also increments the data stream's generation. **Roll over an
-        index alias with a write index** TIP: Prior to Elasticsearch 7.9, you'd typically
-        use an index alias with a write index to manage time series data. Data streams
-        replace this functionality, require less maintenance, and automatically integrate
-        with data tiers. If an index alias points to multiple indices, one of the indices
-        must be a write index. The rollover API creates a new write index for the alias
-        with `is_write_index` set to `true`. The API also `sets is_write_index` to `false`
-        for the previous write index. **Roll over an index alias with one index** If
-        you roll over an index alias that points to only one index, the API creates a
-        new index for the alias and removes the original index from the alias. NOTE:
-        A rollover creates a new index and is subject to the `wait_for_active_shards`
-        setting. **Increment index names for an alias** When you roll over an index alias,
-        you can specify a name for the new index. If you don't specify a name and the
-        current index ends with `-` and a number, such as `my-index-000001` or `my-index-3`,
-        the new index name increments that number. For example, if you roll over an alias
-        with a current index of `my-index-000001`, the rollover creates a new index named
-        `my-index-000002`. This number is always six characters and zero-padded, regardless
-        of the previous index's name. If you use an index alias for time series data,
-        you can use date math in the index name to track the rollover date. For example,
-        you can create an alias that points to an index named `<my-index-{now/d}-000001>`.
-        If you create the index on May 6, 2099, the index's name is `my-index-2099.05.06-000001`.
-        If you roll over the alias on May 7, 2099, the new index's name is `my-index-2099.05.07-000002`.
+        .. raw:: html
+
+          <p>Roll over to a new index.
+          TIP: It is recommended to use the index lifecycle rollover action to automate rollovers.</p>
+          <p>The rollover API creates a new index for a data stream or index alias.
+          The API behavior depends on the rollover target.</p>
+          <p><strong>Roll over a data stream</strong></p>
+          <p>If you roll over a data stream, the API creates a new write index for the stream.
+          The stream's previous write index becomes a regular backing index.
+          A rollover also increments the data stream's generation.</p>
+          <p><strong>Roll over an index alias with a write index</strong></p>
+          <p>TIP: Prior to Elasticsearch 7.9, you'd typically use an index alias with a write index to manage time series data.
+          Data streams replace this functionality, require less maintenance, and automatically integrate with data tiers.</p>
+          <p>If an index alias points to multiple indices, one of the indices must be a write index.
+          The rollover API creates a new write index for the alias with <code>is_write_index</code> set to <code>true</code>.
+          The API also <code>sets is_write_index</code> to <code>false</code> for the previous write index.</p>
+          <p><strong>Roll over an index alias with one index</strong></p>
+          <p>If you roll over an index alias that points to only one index, the API creates a new index for the alias and removes the original index from the alias.</p>
+          <p>NOTE: A rollover creates a new index and is subject to the <code>wait_for_active_shards</code> setting.</p>
+          <p><strong>Increment index names for an alias</strong></p>
+          <p>When you roll over an index alias, you can specify a name for the new index.
+          If you don't specify a name and the current index ends with <code>-</code> and a number, such as <code>my-index-000001</code> or <code>my-index-3</code>, the new index name increments that number.
+          For example, if you roll over an alias with a current index of <code>my-index-000001</code>, the rollover creates a new index named <code>my-index-000002</code>.
+          This number is always six characters and zero-padded, regardless of the previous index's name.</p>
+          <p>If you use an index alias for time series data, you can use date math in the index name to track the rollover date.
+          For example, you can create an alias that points to an index named <code>&lt;my-index-{now/d}-000001&gt;</code>.
+          If you create the index on May 6, 2099, the index's name is <code>my-index-2099.05.06-000001</code>.
+          If you roll over the alias on May 7, 2099, the new index's name is <code>my-index-2099.05.07-000002</code>.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-rollover-index.html>`_
 
@@ -4288,9 +4390,12 @@ class IndicesClient(NamespacedClient):
         verbose: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index segments. Get low-level information about the Lucene segments in index
-        shards. For data streams, the API returns information about the stream's backing
-        indices.
+        .. raw:: html
+
+          <p>Get index segments.
+          Get low-level information about the Lucene segments in index shards.
+          For data streams, the API returns information about the stream's backing indices.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-segments.html>`_
 
@@ -4369,14 +4474,20 @@ class IndicesClient(NamespacedClient):
         ] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index shard stores. Get store information about replica shards in one or
-        more indices. For data streams, the API retrieves store information for the stream's
-        backing indices. The index shard stores API returns the following information:
-        * The node on which each replica shard exists. * The allocation ID for each replica
-        shard. * A unique ID for each replica shard. * Any errors encountered while opening
-        the shard index or from an earlier failure. By default, the API returns store
-        information only for primary shards that are unassigned or have one or more unassigned
-        replica shards.
+        .. raw:: html
+
+          <p>Get index shard stores.
+          Get store information about replica shards in one or more indices.
+          For data streams, the API retrieves store information for the stream's backing indices.</p>
+          <p>The index shard stores API returns the following information:</p>
+          <ul>
+          <li>The node on which each replica shard exists.</li>
+          <li>The allocation ID for each replica shard.</li>
+          <li>A unique ID for each replica shard.</li>
+          <li>Any errors encountered while opening the shard index or from an earlier failure.</li>
+          </ul>
+          <p>By default, the API returns store information only for primary shards that are unassigned or have one or more unassigned replica shards.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-shards-stores.html>`_
 
@@ -4447,39 +4558,38 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Shrink an index. Shrink an index into a new index with fewer primary shards.
-        Before you can shrink an index: * The index must be read-only. * A copy of every
-        shard in the index must reside on the same node. * The index must have a green
-        health status. To make shard allocation easier, we recommend you also remove
-        the index's replica shards. You can later re-add replica shards as part of the
-        shrink operation. The requested number of primary shards in the target index
-        must be a factor of the number of shards in the source index. For example an
-        index with 8 primary shards can be shrunk into 4, 2 or 1 primary shards or an
-        index with 15 primary shards can be shrunk into 5, 3 or 1. If the number of shards
-        in the index is a prime number it can only be shrunk into a single primary shard
-        Before shrinking, a (primary or replica) copy of every shard in the index must
-        be present on the same node. The current write index on a data stream cannot
-        be shrunk. In order to shrink the current write index, the data stream must first
-        be rolled over so that a new write index is created and then the previous write
-        index can be shrunk. A shrink operation: * Creates a new target index with the
-        same definition as the source index, but with a smaller number of primary shards.
-        * Hard-links segments from the source index into the target index. If the file
-        system does not support hard-linking, then all segments are copied into the new
-        index, which is a much more time consuming process. Also if using multiple data
-        paths, shards on different data paths require a full copy of segment files if
-        they are not on the same disk since hardlinks do not work across disks. * Recovers
-        the target index as though it were a closed index which had just been re-opened.
-        Recovers shards to the `.routing.allocation.initial_recovery._id` index setting.
-        IMPORTANT: Indices can only be shrunk if they satisfy the following requirements:
-        * The target index must not exist. * The source index must have more primary
-        shards than the target index. * The number of primary shards in the target index
-        must be a factor of the number of primary shards in the source index. The source
-        index must have more primary shards than the target index. * The index must not
-        contain more than 2,147,483,519 documents in total across all shards that will
-        be shrunk into a single shard on the target index as this is the maximum number
-        of docs that can fit into a single shard. * The node handling the shrink process
-        must have sufficient free disk space to accommodate a second copy of the existing
-        index.
+        .. raw:: html
+
+          <p>Shrink an index.
+          Shrink an index into a new index with fewer primary shards.</p>
+          <p>Before you can shrink an index:</p>
+          <ul>
+          <li>The index must be read-only.</li>
+          <li>A copy of every shard in the index must reside on the same node.</li>
+          <li>The index must have a green health status.</li>
+          </ul>
+          <p>To make shard allocation easier, we recommend you also remove the index's replica shards.
+          You can later re-add replica shards as part of the shrink operation.</p>
+          <p>The requested number of primary shards in the target index must be a factor of the number of shards in the source index.
+          For example an index with 8 primary shards can be shrunk into 4, 2 or 1 primary shards or an index with 15 primary shards can be shrunk into 5, 3 or 1.
+          If the number of shards in the index is a prime number it can only be shrunk into a single primary shard
+          Before shrinking, a (primary or replica) copy of every shard in the index must be present on the same node.</p>
+          <p>The current write index on a data stream cannot be shrunk. In order to shrink the current write index, the data stream must first be rolled over so that a new write index is created and then the previous write index can be shrunk.</p>
+          <p>A shrink operation:</p>
+          <ul>
+          <li>Creates a new target index with the same definition as the source index, but with a smaller number of primary shards.</li>
+          <li>Hard-links segments from the source index into the target index. If the file system does not support hard-linking, then all segments are copied into the new index, which is a much more time consuming process. Also if using multiple data paths, shards on different data paths require a full copy of segment files if they are not on the same disk since hardlinks do not work across disks.</li>
+          <li>Recovers the target index as though it were a closed index which had just been re-opened. Recovers shards to the <code>.routing.allocation.initial_recovery._id</code> index setting.</li>
+          </ul>
+          <p>IMPORTANT: Indices can only be shrunk if they satisfy the following requirements:</p>
+          <ul>
+          <li>The target index must not exist.</li>
+          <li>The source index must have more primary shards than the target index.</li>
+          <li>The number of primary shards in the target index must be a factor of the number of primary shards in the source index. The source index must have more primary shards than the target index.</li>
+          <li>The index must not contain more than 2,147,483,519 documents in total across all shards that will be shrunk into a single shard on the target index as this is the maximum number of docs that can fit into a single shard.</li>
+          <li>The node handling the shrink process must have sufficient free disk space to accommodate a second copy of the existing index.</li>
+          </ul>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-shrink-index.html>`_
 
@@ -4554,8 +4664,11 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Simulate an index. Get the index configuration that would be applied to the specified
-        index from an existing index template.
+        .. raw:: html
+
+          <p>Simulate an index.
+          Get the index configuration that would be applied to the specified index from an existing index template.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-simulate-index.html>`_
 
@@ -4632,8 +4745,11 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Simulate an index template. Get the index configuration that would be applied
-        by a particular index template.
+        .. raw:: html
+
+          <p>Simulate an index template.
+          Get the index configuration that would be applied by a particular index template.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-simulate-template.html>`_
 
@@ -4764,31 +4880,44 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Split an index. Split an index into a new index with more primary shards. * Before
-        you can split an index: * The index must be read-only. * The cluster health status
-        must be green. You can do make an index read-only with the following request
-        using the add index block API: ``` PUT /my_source_index/_block/write ``` The
-        current write index on a data stream cannot be split. In order to split the current
-        write index, the data stream must first be rolled over so that a new write index
-        is created and then the previous write index can be split. The number of times
-        the index can be split (and the number of shards that each original shard can
-        be split into) is determined by the `index.number_of_routing_shards` setting.
-        The number of routing shards specifies the hashing space that is used internally
-        to distribute documents across shards with consistent hashing. For instance,
-        a 5 shard index with `number_of_routing_shards` set to 30 (5 x 2 x 3) could be
-        split by a factor of 2 or 3. A split operation: * Creates a new target index
-        with the same definition as the source index, but with a larger number of primary
-        shards. * Hard-links segments from the source index into the target index. If
-        the file system doesn't support hard-linking, all segments are copied into the
-        new index, which is a much more time consuming process. * Hashes all documents
-        again, after low level files are created, to delete documents that belong to
-        a different shard. * Recovers the target index as though it were a closed index
-        which had just been re-opened. IMPORTANT: Indices can only be split if they satisfy
-        the following requirements: * The target index must not exist. * The source index
-        must have fewer primary shards than the target index. * The number of primary
-        shards in the target index must be a multiple of the number of primary shards
-        in the source index. * The node handling the split process must have sufficient
-        free disk space to accommodate a second copy of the existing index.
+        .. raw:: html
+
+          <p>Split an index.
+          Split an index into a new index with more primary shards.</p>
+          <ul>
+          <li>
+          <p>Before you can split an index:</p>
+          </li>
+          <li>
+          <p>The index must be read-only.</p>
+          </li>
+          <li>
+          <p>The cluster health status must be green.</p>
+          </li>
+          </ul>
+          <p>You can do make an index read-only with the following request using the add index block API:</p>
+          <pre><code>PUT /my_source_index/_block/write
+          </code></pre>
+          <p>The current write index on a data stream cannot be split.
+          In order to split the current write index, the data stream must first be rolled over so that a new write index is created and then the previous write index can be split.</p>
+          <p>The number of times the index can be split (and the number of shards that each original shard can be split into) is determined by the <code>index.number_of_routing_shards</code> setting.
+          The number of routing shards specifies the hashing space that is used internally to distribute documents across shards with consistent hashing.
+          For instance, a 5 shard index with <code>number_of_routing_shards</code> set to 30 (5 x 2 x 3) could be split by a factor of 2 or 3.</p>
+          <p>A split operation:</p>
+          <ul>
+          <li>Creates a new target index with the same definition as the source index, but with a larger number of primary shards.</li>
+          <li>Hard-links segments from the source index into the target index. If the file system doesn't support hard-linking, all segments are copied into the new index, which is a much more time consuming process.</li>
+          <li>Hashes all documents again, after low level files are created, to delete documents that belong to a different shard.</li>
+          <li>Recovers the target index as though it were a closed index which had just been re-opened.</li>
+          </ul>
+          <p>IMPORTANT: Indices can only be split if they satisfy the following requirements:</p>
+          <ul>
+          <li>The target index must not exist.</li>
+          <li>The source index must have fewer primary shards than the target index.</li>
+          <li>The number of primary shards in the target index must be a multiple of the number of primary shards in the source index.</li>
+          <li>The node handling the split process must have sufficient free disk space to accommodate a second copy of the existing index.</li>
+          </ul>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-split-index.html>`_
 
@@ -4880,14 +5009,17 @@ class IndicesClient(NamespacedClient):
         pretty: t.Optional[bool] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Get index statistics. For data streams, the API retrieves statistics for the
-        stream's backing indices. By default, the returned statistics are index-level
-        with `primaries` and `total` aggregations. `primaries` are the values for only
-        the primary shards. `total` are the accumulated values for both primary and replica
-        shards. To get shard-level statistics, set the `level` parameter to `shards`.
-        NOTE: When moving to another node, the shard-level statistics for a shard are
-        cleared. Although the shard is no longer part of the node, that node retains
-        any node-level statistics to which the shard contributed.
+        .. raw:: html
+
+          <p>Get index statistics.
+          For data streams, the API retrieves statistics for the stream's backing indices.</p>
+          <p>By default, the returned statistics are index-level with <code>primaries</code> and <code>total</code> aggregations.
+          <code>primaries</code> are the values for only the primary shards.
+          <code>total</code> are the accumulated values for both primary and replica shards.</p>
+          <p>To get shard-level statistics, set the <code>level</code> parameter to <code>shards</code>.</p>
+          <p>NOTE: When moving to another node, the shard-level statistics for a shard are cleared.
+          Although the shard is no longer part of the node, that node retains any node-level statistics to which the shard contributed.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-stats.html>`_
 
@@ -4990,8 +5122,11 @@ class IndicesClient(NamespacedClient):
         wait_for_active_shards: t.Optional[str] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Unfreeze an index. When a frozen index is unfrozen, the index goes through the
-        normal recovery process and becomes writeable again.
+        .. raw:: html
+
+          <p>Unfreeze an index.
+          When a frozen index is unfrozen, the index goes through the normal recovery process and becomes writeable again.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/unfreeze-index-api.html>`_
 
@@ -5065,7 +5200,11 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Create or update an alias. Adds a data stream or index to an alias.
+        .. raw:: html
+
+          <p>Create or update an alias.
+          Adds a data stream or index to an alias.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/indices-aliases.html>`_
 
@@ -5140,7 +5279,11 @@ class IndicesClient(NamespacedClient):
         body: t.Optional[t.Dict[str, t.Any]] = None,
     ) -> ObjectApiResponse[t.Any]:
         """
-        Validate a query. Validates a query without running it.
+        .. raw:: html
+
+          <p>Validate a query.
+          Validates a query without running it.</p>
+
 
         `<https://www.elastic.co/guide/en/elasticsearch/reference/8.17/search-validate.html>`_