-
Notifications
You must be signed in to change notification settings - Fork 98
fix(NODE-5053): enforce empty map for kmsProvider auto credentials #565
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
c621704
fix(NODE-5053): enforce empty map for kmsProvider auto credentials
nbbeeken eed6850
fix: return kmsProviders from loadAWSCredentials
nbbeeken 7434d11
test: exports
nbbeeken 19430f4
all keys check
nbbeeken 6f48b07
fixes to providers tests
nbbeeken f49c676
extension coverage
nbbeeken File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
'use strict'; | ||
|
||
const { expect } = require('chai'); | ||
const mongodbClientEncryption = require('../lib/index'); | ||
|
||
// Update this as you add exports, helps double check we don't accidentally remove something | ||
// since not all tests import from the root public export | ||
const EXPECTED_EXPORTS = [ | ||
'extension', | ||
'MongoCryptError', | ||
'MongoCryptCreateEncryptedCollectionError', | ||
'MongoCryptCreateDataKeyError', | ||
'AutoEncrypter', | ||
'ClientEncryption' | ||
]; | ||
|
||
describe('mongodb-client-encryption entrypoint', () => { | ||
it('should export all and only the expected keys in expected_exports', () => { | ||
expect(mongodbClientEncryption).to.have.all.keys(EXPECTED_EXPORTS); | ||
}); | ||
|
||
it('extension returns an object equal in shape to the default except for extension', () => { | ||
const extensionResult = mongodbClientEncryption.extension(require('mongodb')); | ||
const expectedExports = EXPECTED_EXPORTS.filter(exp => exp !== 'extension'); | ||
const exportsDefault = Object.keys(mongodbClientEncryption).filter(exp => exp !== 'extension'); | ||
expect(extensionResult).to.have.all.keys(expectedExports); | ||
expect(extensionResult).to.have.all.keys(exportsDefault); | ||
}); | ||
}); | ||
durran marked this conversation as resolved.
Show resolved
Hide resolved
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Btw, it is so nice that this package does dependency injection for the driver package – It might even be worth adapting that to this dependency as well … :)
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.
How come you think this is a beneficial pattern? The DI for the driver is something I've wanted to remove for a while
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.
Well, from a very practical point, it’s just a necessity in cases where the driver is bundled into something but this package isn’t (which would be common in bundling scenarios given that this package is a native addon package).
But also just philosophically (and I’m pretty sure you already know this), I think DI is a great design pattern that solves more issues than it creates 🙂
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.
Just to clarify, this thought is not directly related to the changes in this PR and should absolutely not block it :)
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.
We should consider this though, using it for testing too could be 🔥
For GCP we don't plan to use an SDK (and likely not for azure either) so this would only be for AWS but still, valid use case even for one dep.