-
Notifications
You must be signed in to change notification settings - Fork 1.8k
test(NODE-2422): Validate that mongocryptd is not spawned if bypassAutoEncryption=true #3662
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
test(NODE-2422): Validate that mongocryptd is not spawned if bypassAutoEncryption=true #3662
Conversation
…d' into NODE-2422/validate_that_mongocryptd_not_spawned_if_bypassAutoEncrypt_is_true
…ned_if_bypassAutoEncrypt_is_true
test/integration/client-side-encryption/client_side_encryption.prose.test.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a lot of failing tests on this PR specifically, have they all been reviewed?
test/integration/client-side-encryption/client_side_encryption.prose.test.js
Outdated
Show resolved
Hide resolved
…ned_if_bypassAutoEncrypt_is_true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM assuming all the CI failures are accounted for
Win/Node 14 issues unrelated to this PR. |
Description
What is changing?
Is there new documentation needed for these changes?
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