Update dependency @elastic/elasticsearch to ^8.0.0-canary.22 (master)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@elastic/elasticsearch (source)	^8.0.0-canary.21 -> ^8.0.0-canary.22

---

Release Notes

elastic/elasticsearch-js

v8.0.0-canary.22

Compare Source

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: b3b9390
• Storybooks not built
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures

Failed CI Steps

• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies
• Error signal

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [48315da]

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[pgayvallet]

From the build logs:

11:33:14   info [bazel] packages/kbn-securitysolution-es-utils/src/delete_all_index/index.ts:31:5 - error TS2578: Unused '@ts-expect-error' directive.
11:33:14   info [bazel] 
11:33:14   info [bazel] 31     // @ts-expect-error status doesn't exist on response
11:33:14   info [bazel]        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11:33:14   info [bazel] 
11:33:14   info [bazel] packages/kbn-securitysolution-es-utils/src/elasticsearch_client/index.ts:12:35 - error TS2307: Cannot find module '@elastic/elasticsearch/api/kibana' or its corresponding type declarations.
11:33:14   info [bazel] 
11:33:14   info [bazel] 12 import type { KibanaClient } from '@elastic/elasticsearch/api/kibana';
11:33:14   info [bazel]                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11:33:14   info [bazel] 
11:33:14   info [bazel] packages/kbn-securitysolution-es-utils/src/elasticsearch_client/index.ts:18:8 - error TS2307: Cannot find module '@elastic/elasticsearch/lib/Transport' or its corresponding type declarations.
11:33:14   info [bazel] 
11:33:14   info [bazel] 18 } from '@elastic/elasticsearch/lib/Transport';
11:33:14   info [bazel]           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11:33:14   info [bazel] 

The first one is a type fix, which is good, but the second and third errors are types that are no longer here.

@delvedor were the types moved elsewhere, or is this more impacting that this?

[delvedor]

@pgayvallet the transport has been moved into its own package: @elastic/transport.

The new Kibana types has been moved here: @elastic/elasticsearch-canary/lib/api/kibana

[mshustov]

The new Kibana types has been moved here: @elastic/elasticsearch-canary/lib/api/kibana

@delvedor Is it a recommended way to import Transport* types? Why not from the root of the package?

import type {
  ApiResponse,
  TransportRequestOptions,
  TransportRequestParams,
  TransportRequestPromise,
--- } from '@elastic/elasticsearch/lib/Transport';
+++ } from '@elastic/elasticsearch';

[pgayvallet]

Okay, there are some significant changes in the transport types. Unsure of the amount of work required to get this green.

[delvedor]

@delvedor Is it a recommended way to import Transport* types? Why not from the root of the package?

Yes, you should import them from that package. Re-exporting could go out of sync, and if you need the transport types, very likely you also need to use something from the transport module in any case.

[mshustov]

Closing. I'm going to work on it in #108387

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (^8.0.0-canary.22). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.