Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SKR changes from Arch Board meeting #25002

Closed
heaths opened this issue Oct 22, 2021 · 1 comment
Closed

SKR changes from Arch Board meeting #25002

heaths opened this issue Oct 22, 2021 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Milestone
[2021] November

Comments

@heaths
Copy link
Member

heaths commented Oct 22, 2021

After discussion with the Key Vault and Managed HSM teams on Secure Key Release, we have arrived at the following changes for SKR models to be done in the SDK (the service will not be renaming in the swagger):

  • KeyReleasePolicy.Data -> KeyReleasePolicy.EncodedPolicy
  • The target parameter in KeyClient.ReleaseKey -> targetAttestationToken

The ReleaseKeyResult.Value property should be left as-is.
@heaths heaths added Client This issue points to a problem in the data-plane of the library. KeyVault labels Oct 22, 2021
@heaths heaths added this to the [2021] November milestone Oct 22, 2021
@vcolin7
Copy link
Member

vcolin7 commented May 13, 2022

Applied all Arch Board suggestions in #26910 and #27442.

@vcolin7 vcolin7 closed this as completed May 13, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Projects
Azure SDK for Key Vault
Archived in project
Milestone
[2021] November
Development

No branches or pull requests
2 participants
@heaths @vcolin7