[keyvault] Migrate remaining Key Vault packages to keyvault-common #26875
Conversation
|
API change check API changes are not detected in this pull request. |
|
Hi @timovv. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
github-actions
bot
added
the
no-recent-activity
timovv
removed
the
no-recent-activity
|
Hi @timovv. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
github-actions
bot
added
the
no-recent-activity
github-actions
bot
removed
the
no-recent-activity
There was a problem hiding this comment.
LGTM , I used https://github.com/Azure/azure-sdk-for-js/pull/23737/files as the comparison (minus the browser replacements since admin does not have browser support)
Packages impacted by this PR
@azure/keyvault-keys@azure/keyvault-secretsIssues associated with this PR
keyvault-commonas a package #22705Describe the problem that is addressed by this PR
Noticed that I never actually finished the job for these two packages (oops!) so this PR brings Keys and Secrets up to speed with the latest keyvault-common goodness