def resolve_cluster(
        self,
        *,
        name: t.Optional[t.Union[str, t.Sequence[str]]] = None,
        allow_no_indices: t.Optional[bool] = None,
        error_trace: t.Optional[bool] = None,
        expand_wildcards: t.Optional[
            t.Union[
                t.Sequence[
                    t.Union[str, t.Literal["all", "closed", "hidden", "none", "open"]]
                ],
                t.Union[str, t.Literal["all", "closed", "hidden", "none", "open"]],
            ]
        ] = None,
        filter_path: t.Optional[t.Union[str, t.Sequence[str]]] = None,
        human: t.Optional[bool] = None,
        ignore_throttled: t.Optional[bool] = None,
        ignore_unavailable: t.Optional[bool] = None,
        pretty: t.Optional[bool] = None,
        timeout: t.Optional[t.Union[str, t.Literal[-1], t.Literal[0]]] = None,
    ) -> ObjectApiResponse[t.Any]:
        """
        .. raw:: html

          <p>Resolve the cluster.</p>
          <p>Resolve the specified index expressions to return information about each cluster, including the local &quot;querying&quot; cluster, if included.
          If no index expression is provided, the API will return information about all the remote clusters that are configured on the querying cluster.</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 specified in the index expression. Note that this endpoint actively attempts to contact the remote clusters, unlike the <code>remote/info</code> endpoint.</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>
          <h2>Note on backwards compatibility</h2>
          <p>The ability to query without an index expression was added in version 8.18, so when
          querying remote clusters older than that, the local cluster will send the index
          expression <code>dummy*</code> to those remote clusters. Thus, if an errors occur, you may see a reference
          to that index expression even though you didn't request it. If it causes a problem, you can
          instead include an index expression like <code>*:*</code> to bypass the issue.</p>
          <h2>Advantages of using this endpoint before a cross-cluster search</h2>
          <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>
          <h2>Test availability of remote clusters</h2>
          <p>The <code>remote/info</code> endpoint is commonly used to test whether the &quot;local&quot; cluster (the cluster being queried) is connected to its remote clusters, but it does not necessarily reflect whether the remote cluster is available or not.
          The remote cluster may be available, while the local cluster is not currently connected to it.</p>
          <p>You can use the <code>_resolve/cluster</code> API to attempt to reconnect to remote clusters.
          For example with <code>GET _resolve/cluster</code> or <code>GET _resolve/cluster/*:*</code>.
          The <code>connected</code> field in the response will indicate whether it was successful.
          If a connection was (re-)established, this will also cause the <code>remote/info</code> endpoint to now indicate a connected status.</p>


        `<https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-cluster>`_

        :param name: A comma-separated list of names or index patterns for the indices,
            aliases, and data streams to resolve. Resources on remote clusters can be
            specified using the `<cluster>`:`<name>` syntax. Index and cluster exclusions
            (e.g., `-cluster1:*`) are also supported. If no index expression is specified,
            information about all remote clusters configured on the local cluster is
            returned without doing any index matching
        :param allow_no_indices: If false, the request returns an error if any wildcard
            expression, index alias, or `_all` value targets only missing or closed indices.
            This behavior applies even if the request targets other open indices. For
            example, a request targeting `foo*,bar*` returns an error if an index starts
            with `foo` but no index starts with `bar`. NOTE: This option is only supported
            when specifying an index expression. You will get an error if you specify
            index options to the `_resolve/cluster` API endpoint that takes no index
            expression.
        :param expand_wildcards: Type of index that wildcard patterns can match. If the
            request can target data streams, this argument determines whether wildcard
            expressions match hidden data streams. Supports comma-separated values, such
            as `open,hidden`. Valid values are: `all`, `open`, `closed`, `hidden`, `none`.
            NOTE: This option is only supported when specifying an index expression.
            You will get an error if you specify index options to the `_resolve/cluster`
            API endpoint that takes no index expression.
        :param ignore_throttled: If true, concrete, expanded, or aliased indices are
            ignored when frozen. NOTE: This option is only supported when specifying
            an index expression. You will get an error if you specify index options to
            the `_resolve/cluster` API endpoint that takes no index expression.
        :param ignore_unavailable: If false, the request returns an error if it targets
            a missing or closed index. NOTE: This option is only supported when specifying
            an index expression. You will get an error if you specify index options to
            the `_resolve/cluster` API endpoint that takes no index expression.
        :param timeout: The maximum time to wait for remote clusters to respond. If a
            remote cluster does not respond within this timeout period, the API response
            will show the cluster as not connected and include an error message that
            the request timed out. The default timeout is unset and the query can take
            as long as the networking layer is configured to wait for remote clusters
            that are not responding (typically 30 seconds).
        """
        __path_parts: t.Dict[str, str]
        if name not in SKIP_IN_PATH:
            __path_parts = {"name": _quote(name)}
            __path = f'/_resolve/cluster/{__path_parts["name"]}'
        else:
            __path_parts = {}
            __path = "/_resolve/cluster"
        __query: t.Dict[str, t.Any] = {}
        if allow_no_indices is not None:
            __query["allow_no_indices"] = allow_no_indices
        if error_trace is not None:
            __query["error_trace"] = error_trace
        if expand_wildcards is not None:
            __query["expand_wildcards"] = expand_wildcards
        if filter_path is not None:
            __query["filter_path"] = filter_path
        if human is not None:
            __query["human"] = human
        if ignore_throttled is not None:
            __query["ignore_throttled"] = ignore_throttled
        if ignore_unavailable is not None:
            __query["ignore_unavailable"] = ignore_unavailable
        if pretty is not None:
            __query["pretty"] = pretty
        if timeout is not None:
            __query["timeout"] = timeout
        __headers = {"accept": "application/json"}
        return self.perform_request(  # type: ignore[return-value]
            "GET",
            __path,
            params=__query,
            headers=__headers,
            endpoint_id="indices.resolve_cluster",
            path_parts=__path_parts,
        )

        .. raw:: html

          <p>Resolve the cluster.</p>
          <p>Resolve the specified index expressions to return information about each cluster, including the local &quot;querying&quot; cluster, if included.
          If no index expression is provided, the API will return information about all the remote clusters that are configured on the querying cluster.</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 specified in the index expression. Note that this endpoint actively attempts to contact the remote clusters, unlike the <code>remote/info</code> endpoint.</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>
          <h2>Note on backwards compatibility</h2>
          <p>The ability to query without an index expression was added in version 8.18, so when
          querying remote clusters older than that, the local cluster will send the index
          expression <code>dummy*</code> to those remote clusters. Thus, if an errors occur, you may see a reference
          to that index expression even though you didn't request it. If it causes a problem, you can
          instead include an index expression like <code>*:*</code> to bypass the issue.</p>
          <h2>Advantages of using this endpoint before a cross-cluster search</h2>
          <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>
          <h2>Test availability of remote clusters</h2>
          <p>The <code>remote/info</code> endpoint is commonly used to test whether the &quot;local&quot; cluster (the cluster being queried) is connected to its remote clusters, but it does not necessarily reflect whether the remote cluster is available or not.
          The remote cluster may be available, while the local cluster is not currently connected to it.</p>
          <p>You can use the <code>_resolve/cluster</code> API to attempt to reconnect to remote clusters.
          For example with <code>GET _resolve/cluster</code> or <code>GET _resolve/cluster/*:*</code>.
          The <code>connected</code> field in the response will indicate whether it was successful.
          If a connection was (re-)established, this will also cause the <code>remote/info</code> endpoint to now indicate a connected status.</p>


        `<https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-cluster>`_

        :param name: A comma-separated list of names or index patterns for the indices,
            aliases, and data streams to resolve. Resources on remote clusters can be
            specified using the `<cluster>`:`<name>` syntax. Index and cluster exclusions
            (e.g., `-cluster1:*`) are also supported. If no index expression is specified,
            information about all remote clusters configured on the local cluster is
            returned without doing any index matching
        :param allow_no_indices: If false, the request returns an error if any wildcard
            expression, index alias, or `_all` value targets only missing or closed indices.
            This behavior applies even if the request targets other open indices. For
            example, a request targeting `foo*,bar*` returns an error if an index starts
            with `foo` but no index starts with `bar`. NOTE: This option is only supported
            when specifying an index expression. You will get an error if you specify
            index options to the `_resolve/cluster` API endpoint that takes no index
            expression.
        :param expand_wildcards: Type of index that wildcard patterns can match. If the
            request can target data streams, this argument determines whether wildcard
            expressions match hidden data streams. Supports comma-separated values, such
            as `open,hidden`. Valid values are: `all`, `open`, `closed`, `hidden`, `none`.
            NOTE: This option is only supported when specifying an index expression.
            You will get an error if you specify index options to the `_resolve/cluster`
            API endpoint that takes no index expression.
        :param ignore_throttled: If true, concrete, expanded, or aliased indices are
            ignored when frozen. NOTE: This option is only supported when specifying
            an index expression. You will get an error if you specify index options to
            the `_resolve/cluster` API endpoint that takes no index expression.
        :param ignore_unavailable: If false, the request returns an error if it targets
            a missing or closed index. NOTE: This option is only supported when specifying
            an index expression. You will get an error if you specify index options to
            the `_resolve/cluster` API endpoint that takes no index expression.
        :param timeout: The maximum time to wait for remote clusters to respond. If a
            remote cluster does not respond within this timeout period, the API response
            will show the cluster as not connected and include an error message that
            the request timed out. The default timeout is unset and the query can take
            as long as the networking layer is configured to wait for remote clusters
            that are not responding (typically 30 seconds).
        
elasticsearch/_sync/client/indices.py