-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
feat(NODE-6391): Add timeoutMS support to explicit encryption #4269
Conversation
Co-authored-by: Warren James <[email protected]>
Co-authored-by: Bailey Pearson <[email protected]>
Co-authored-by: Neal Beeken <[email protected]> Co-authored-by: Bailey Pearson <[email protected]>
Co-authored-by: Neal Beeken <[email protected]>
…4243) Co-authored-by: Warren James <[email protected]> Co-authored-by: Neal Beeken <[email protected]> Co-authored-by: Bailey Pearson <[email protected]>
There is an existing patch(es) for this commit SHA: Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'. |
3591368
to
a645d9f
Compare
Co-authored-by: Warren James <[email protected]>
Co-authored-by: Warren James <[email protected]>
Co-authored-by: Warren James <[email protected]>
Description
What is changing?
Add timeoutMS support to
ClientEncryptionOptions
the following ClientEncryption helper functions:
Implemented spec prose tests for the above (createDataKey, encrypt, decrypt)
Add integration test for createEncryptedCollection and CSOT
Add unit tests for ClientEncryption getting a timeoutMS value from client and/or ClientEncryptionOptions
Is there new documentation needed for these changes?
During release
What is the motivation for this change?
Spec Compliance
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript