-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(NODE-3728): Allow to pass authorizedCollections option to the db.listCollections method
#3021
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-3728): Allow to pass authorizedCollections option to the db.listCollections method
#3021
Conversation
6152200 to
76e51b2
Compare
|
@gribnoysup There was a CI issue that blocked all tests from running which necessitated a change to main for the fix, could you rebase your branch to pull them in here? |
….listCollections method
76e51b2 to
516e28d
Compare
|
Thanks for the heads-up @dariakp! Rebased on |
dariakp
left a comment
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 a couple suggested changes to (hopefully) better match the test descriptions to what is being tested
dariakp
left a comment
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.
Thank you!
…`db.listCollections` method (#3021)
Description
This patch allows to pass
authorizedCollectionsoption when usingdb.listCollectionsmethodWhat is changing?
ListCollectionsOperationclass now hasauthorizedCollectionsdefined and handled in a similar fashion to thenameOnlyoptionIs there new documentation needed for these changes?
Not needed (I think)
What is the motivation for this change?
This adds support for a
listCollectionscommand option that is helpful when you want to fetch a list of collections for the user that might not have enough privileges to list them otherwise. A full description can be found in thelistCollectionscommand docsDouble check the following
npm run check:lintscriptnpm run testscript<type>(NODE-xxxx)<!>: <description>