Unsure if there's a reason why we're only letting server access ServerConfig. The sync-identity-search command currently requires the ServerConfig for the opensearch endpoint

It matches and error! logs if error result and discards ok result.

Here's the code:

pub fn consume_error<T>(result: Result<T, Error>) {
  match result {
    Ok(_) => (),
    Err(e) => {
      error!("{}", e);
    }
  }
}

If you mean confirming inside the code, we can query the opensearch domain and check if the number of hits returned is zero. I can add in the next rebase

application/x-ndjson is for the _bulk endpoint. The _delete_by_query endpoint only requires application/json.

From what I understand, elastic and opensearch uses x-ndjson for performance purposes. In most guides, x-ndjson is used including on the official opensearch api docs.

The latest version of Elastic seems to support json as well but x-ndjson seems to be the most generally supported.

I believe it's actually | for match pattern. || gives me a compile error and requires |

how about this comment?

Yep. Thanks