Resolve architect board feedback for Key Vault #17992
Labels
Client
This issue points to a problem in the data-plane of the library.
KeyVault
late-blocker
Changes based on review feedback before imminent release.
Milestone
Here are a few things that came up during the archboard review. Note that there is a discussion about whether to expose a
LocalCryptographyClient
or make it a "mode" ofCryptographyClient
, but that should only apply to .NET and Java. That is not listed below as prototyping is necessary. But #18575 is tracking that work.EncryptOptions
toEncryptParameters
.DecryptOptions
toDecryptParameters
.AdditionalAuthenticatedData
should be a read-only property (no setters).KeyVaultKeyIdentifier
(as well as for secrets and certificates) should not have "parse" methods, but instead take the URI into the constructor/creator. This pattern will, of course, vary from language to language.JsonWebKey
are settable (came up indirectly, but this should be the case already).KeyVault*Identifier
structs should implementIEquatable<T>
.The text was updated successfully, but these errors were encountered: