Skip to content

Conversation

addaleax
Copy link
Collaborator

No description provided.

@addaleax addaleax force-pushed the 442-dev branch 2 times, most recently from 7333951 to 6c80b4a Compare May 17, 2021 16:10
@addaleax addaleax marked this pull request as ready for review May 17, 2021 16:10
@addaleax addaleax force-pushed the 442-dev branch 2 times, most recently from 8821cc0 to c6a160a Compare May 18, 2021 11:29
Copy link
Collaborator

@mcasimir mcasimir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

fsConstants.COPYFILE_FICLONE);
} else {
await fs.copyFile(
path.resolve(__dirname, '..', '..', '..', '..', 'scripts', 'no-mongocryptd.sh'),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How is this going to work? Will it affect something that mongosh does automatically or is rather there if users tries to run mongocryptd manually?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, mongosh won’t be able to do automatic FLE for the time being. The exposed binary is still named mongocryptd-mongosh, so I don’t think it’s something the user would run by accident.

@addaleax addaleax merged commit 93b7f7c into main May 19, 2021
@addaleax addaleax deleted the 442-dev branch May 19, 2021 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants