Remove algorithm string from encryptionKeyWrapMetadata and converting MicrosoftDataEncryptionException to CosmosException #20845
Conversation
…onException to CosmosException
simplynaveen20
requested review from
FabianMeiswinkel,
kirankumarkolli,
kushagraThapar,
mbhaskar,
milismsft,
moderakh and
xinlian12
as code owners
ghost
added
the
simplynaveen20
added
the
azure-cosmos-encryption
simplynaveen20
changed the title
Removing BridgeInternal need CosmosBuilderAccessor for all the bridge internal usages, or redesigning Cosmos project itself , and it is not in scope of this PR. We need to brainstorm separately |
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
… MicrosoftDataEncryptionException to CosmosException (#20845) * Adding type on encryptionMetadata and coverting MicrosoftDataEncryptionException to CosmosException * correction class name of logger * Increasing the encryption length support to 8000 from 1024 * adding test case and fixing nested pojo array issue * updating plain text test * reverting change for encryptionKeyWrapMatadata * removing pojo to test plain text * updating test flow for new emulator * disabling asyncChangeFeed_fromNow_fullFidelity_forFullRange * fixing test for new emulator
Remove algorithm string from EncryptionKeyWrapMetadata and converting MicrosoftDataEncryptionException to CosmosException.
Also fixing bug around encryption create item throw error for nested object array field encryption.
This will also increase the encryption length from 1024 to max 8000 which AAP java support at this time.
closes #20374
closes ##20899
closed #20875
Note: Need to a add test around Plaintext, once I verify this from .NET crew