[KeyVault] - Remove KeyOperationsOptions from public API #14930
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
KeyOperationOptions
from cryptography API and useCryptographyOptions
everywhereWhy
KeyOperationsOptions
was used as a common placeholder foriv
,additionalAuthenticatedData
, andauthenticationTag
up until very recently: https://github.com/Azure/azure-sdk-for-js/pull/13889/files#diff-7e7a216d0920c250e6742ecece9de13be1712657c97776fbfbfec386896cab13L141-L155Because we moved to using
EncryptParameters
andDecryptParameters
for these parameters we no longer need a common type for a subset of cryptography operations. This PR just cleans up the public API a bit before we GA.