[KeyVault] Regenerate @azure/keyvault to address customer issues #6187
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change regenerates the
@azure/keyvault
library usingautorest.typescript
4.2.3 so that it picks upms-rest-js
2.0. This change is needed to alleviate some customer reported issues with that library. We'll also be deprecating this library after the hotfix update.Tasks
Verify that issues [KeyVault] Update @azure/ms-rest-azure-js to 2.0.0 in @azure/keyvault #4530 and [KeyVault] - Types of property signRequest are incompatible (outdated ms-rest-js 1.0 reference) #4793 are fixed with this change@azure/keyvault
package with the commandnpm deprecate @azure/keyvault "This package is deprecated. Please use @azure/keyvault-keys and @azure/keyvault-secrets instead."