You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sdk/keyvault/keyvault-certificates/migration-guide.md
+29-29Lines changed: 29 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ Familiarity with the `azure-keyvault` package is assumed. For those new to the K
6
6
7
7
## Table of contents
8
8
9
-
*[Migration benefits](#migration-benefits)
10
-
*[Important changes](#important-changes)
11
-
-[Separate packages and clients](#separate-packages-and-clients)
12
-
-[Client constructors](#client-constructors)
13
-
-[Create a certificate](#create-a-certificate)
14
-
-[Retrieve a certificate](#retrieve-a-certificate)
15
-
-[List properties of certificates](#list-properties-of-certificates)
16
-
-[Delete a certificate](#delete-a-certificate)
17
-
*[Additional samples](#additional-samples)
9
+
-[Migration benefits](#migration-benefits)
10
+
-[Important changes](#important-changes)
11
+
-[Separate packages and clients](#separate-packages-and-clients)
12
+
-[Client constructors](#client-constructors)
13
+
-[Create a certificate](#create-a-certificate)
14
+
-[Retrieve a certificate](#retrieve-a-certificate)
15
+
-[List properties of certificates](#list-properties-of-certificates)
16
+
-[Delete a certificate](#delete-a-certificate)
17
+
-[Additional samples](#additional-samples)
18
18
19
19
## Migration benefits
20
20
@@ -27,6 +27,7 @@ To try and improve the development experience across Azure services, a set of un
27
27
### Cross Service SDK improvements
28
28
29
29
The modern Key Vault client libraries also share some of the cross-service improvements made to the Azure development experience, such as:
30
+
30
31
- Using the new `@azure/identity` library to share a single authentication approach between clients.
31
32
- A unified logging and diagnostics pipeline that offers a common view of the activities across each of the client libraries.
32
33
- The use of promises rather than callbacks for a simplified programming experience.
@@ -36,7 +37,7 @@ The modern Key Vault client libraries also share some of the cross-service impro
36
37
37
38
### Separate packages and clients
38
39
39
-
In the interest of simplifying the API for working with Key Vault keys, secrets and certificates, the `azure-keyvault`package is split into separate packages.
40
+
In the interest of simplifying the API for working with Key Vault keys, secrets and certificates, the `azure-keyvault` package is split into separate packages.
40
41
41
42
-[`@azure/keyvault-keys`][kvk-npm] contains `KeyClient` for working with Key Vault keys, and `CryptographyClient` for performing cryptographic operations.
42
43
-[`@azure/keyvault-secrets`][kvs-npm] contains `SecretClient` for working with Key Vault secrets.
@@ -51,20 +52,16 @@ Across all of the new Azure client libraries, clients consistently take an endpo
51
52
Previously in `azure-keyvault` you could create a `KeyVaultClient` by using credentials from `ms-rest-azure` (up to the version `^2.6.0`. Higher versions are not supported).
@@ -28,6 +28,7 @@ To try and improve the development experience across Azure services, a set of un
28
28
### Cross Service SDK improvements
29
29
30
30
The modern Key Vault client libraries also share some of the cross-service improvements made to the Azure development experience, such as:
31
+
31
32
- Using the new `@azure/identity` library to share a single authentication approach between clients.
32
33
- A unified logging and diagnostics pipeline that offers a common view of the activities across each of the client libraries.
33
34
- The use of promises rather than callbacks for a simplified programming experience.
@@ -37,7 +38,7 @@ The modern Key Vault client libraries also share some of the cross-service impro
37
38
38
39
### Separate packages and clients
39
40
40
-
In the interest of simplifying the API for working with Key Vault keys, secrets and certificates, the `azure-keyvault`package is split into separate packages.
41
+
In the interest of simplifying the API for working with Key Vault keys, secrets and certificates, the `azure-keyvault` package is split into separate packages.
41
42
42
43
-[`@azure/keyvault-keys`][kvk-npm] contains `KeyClient` for working with Key Vault keys, and `CryptographyClient` for performing cryptographic operations.
43
44
-[`@azure/keyvault-secrets`][kvs-npm] contains `SecretClient` for working with Key Vault secrets.
@@ -51,22 +52,17 @@ Across all of the new Azure client libraries, clients consistently take an endpo
51
52
52
53
Previously in `azure-keyvault` you could create a `KeyVaultClient` by using credentials from `ms-rest-azure` (up to the version `^2.6.0`. Higher versions are not supported).
0 commit comments