Skip to content
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-6507): generate encryption configuration on mongoose connect #6

Draft
wants to merge 1 commit into
base: NODE-6506-add-support-for-encrypted-schemas
Choose a base branch
from

Conversation

baileympearson
Copy link

@baileympearson baileympearson commented Jan 14, 2025

Summary

Automatically generate encryptedFieldMaps and schemaMaps when connecting a Mongoose connection that has schemas configured for CSFLE or QE.

Includes changes from #5 and Automattic#15139.
Examples

See encryption.test.ts in the PR for integration test examples.

@baileympearson baileympearson force-pushed the NODE-6507-generate-schema-maps branch from 411e69d to ebe3d06 Compare January 14, 2025 22:11
@baileympearson baileympearson changed the title Node 6507 generate schema maps feat(NODE-6507): generate encryption configuration on mongoose connect Jan 17, 2025
@baileympearson baileympearson force-pushed the NODE-6507-generate-schema-maps branch from ebe703a to be4563e Compare January 23, 2025 22:48
@baileympearson baileympearson changed the base branch from master to NODE-6506-add-support-for-encrypted-schemas January 23, 2025 22:49
@@ -1083,7 +1083,7 @@ Connection.prototype.on = function on(event, callback) {
// to avoid uncaught exceptions when using `on('error')`. See gh-14377.
Connection.prototype.once = function on(event, callback) {
if (event === 'error' && this.$initialConnection) {
this.$initialConnection.catch(() => {});
this.$initialConnection.catch(() => { });
Copy link
Member

Choose a reason for hiding this comment

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

Please avoid making these sort of minor style changes, they make review difficult and may cause linter issues

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