-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support key export from Key Vault #11029
Comments
Note from Heath, from the teams chat:
|
😉 |
I didn't see that on time! Thank you! |
I'll push this for next month's release due to time budget. |
Maor is currently assigned to the update and cleanup of the Key Vault Admin API. We won't be releasing export/release this month though, so we will likely push this issue for a later date, but in the mean time I'll keep this issue open so Maor can decide. |
This should be moved out of February GA and done for 7.3-preview service version. |
I created #16086 to support SKR. Key Export is not yet ready on the service side. Moving this to backlog |
This doesn't need to be tracked, let's add a new task when key export is ready on the service side. |
For Key Vault 7.2-preview, we need to add support to export keys. This would be a method like
KeyClient.ExportKey
that takes the key name, key version (both required), and a body with theKeyExportParameters
model found in the link below. This only has a single required property namedenvironment
(model property:env
), so we should take this as a parameter. This returns aKeyVaultKey
(modelKeyBundle
).This requires a number of other changes:
Exportable
boolean property toKeyProperties
.ReleasePolicy
property toKeyProperties
of typeKeyReleasePolicy
.PublicExponent
integer property toCreateKeyOptions
.KeyOperation
enum. This will correctly impact theCreateKeyOptions
class and theKeyClient.UpdateKey
method..ReleasePolicy
property toCreateKeyOptions
.ReleasePolicy
property toImportKeyOptions
.See the service version 7.1 -> 7.2-preview diff 🔒 for details.
The text was updated successfully, but these errors were encountered: