Azure/azure-sdk-for-js @azure/keyvault-keys

4.2.0-beta.5 (2021-04-06)

Added local cryptography support for encryption / decryption for A128CBCPAD, A192CBCPAD, and A256CBCPAD.
For AES-CBC encryption we will now generate an IV if the user did not pass it in, making iv optional for those parameters.
Improved tracing across the various KeyVault libraries. By switching to a consistent naming convention, ensuring spans are always closed appropriately, and setting the correct status when an operation errors developers can expect an improved experience when enabling distributed tracing.
- We now ensure tracing spans are properly closed with an appropriate status when an operation throws an exception.
- If a traced operation throws an exception we will now properly record the exception message in the tracing span.
- Finally, naming conventions have been standardized across the KeyVault libraries taking the format of Azure.KeyVault.<PACKAGE NAME>.<CLIENT NAME>.
Fixed an issue where retrying a failed initial Key Vault request may result in an empty body.
[Breaking] Removed the now unused LocalCryptographyAlgorithmName type (Added in 4.2.0-beta.1 to support LocalCryptographyClient and unused since 4.2.0-beta.4)
Updated CryptographyClient to ensure that any local cryptography error is properly handled. We will now try to perform the operation locally where we can but fallback to KeyVault if the local operation fails.