Skip to content

[keyvault] remove dependency on @azure/core-http-compat #36920

@jeremymeng

Description

@jeremymeng

It appears that current version of keyvault packages only uses a type from @azure/core-http-compat

keyvault-keys/src/keysModels.ts:5:import type { ExtendedCommonClientOptions } from "@azure/core-http-compat";
keyvault-secrets/src/secretsModels.ts:5:import type { ExtendedCommonClientOptions } from "@azure/core-http-compat";
keyvault-certificates/src/certificatesModels.ts:6:import type { ExtendedCommonClientOptions } from "@azure/core-http-compat";

It's better to define that inline if there's no runtime dependency on @azure/core-http-compat any more.

Metadata

Metadata

Labels

ClientThis issue points to a problem in the data-plane of the library.KeyVaultneeds-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.

Type

No type

Projects

Status

Untriaged

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions