feat: Add support for MongoDB databaseOptions keys minPoolSize, connectTimeoutMS, socketTimeoutMS, autoSelectFamily, autoSelectFamilyAttemptTimeout

[pocketcolin]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

NOTE: This is a clone of #9522 so that the update can go out in 7.x.x in addition to 8.

9523

Closes: 9523

Approach

As discussed in #9211, the decision was made to maintain a list of valid database options for the Parse config that can be passed to MongoDB. There are many options (46 in total) and this PR adds 3 more that I was using. This approach just follows the same approach used in #9213

Tasks

• Add tests

[parse-github-assistant]

Thanks for opening this pull request!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.50%. Comparing base (6114cd9) to head (b4364f7).
Report is 5 commits behind head on release-7.x.x.

Additional details and impacted files

@@                Coverage Diff                @@
##           release-7.x.x    #9577      +/-   ##
=================================================
- Coverage          93.51%   93.50%   -0.02%     
=================================================
  Files                186      186              
  Lines              14804    14804              
=================================================
- Hits               13844    13842       -2     
- Misses               960      962       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mtrezza]

It seems that this PR is not a clone of the Parse Server 8 PR, as there are more options in this PR, is that correct, and if yes, why?

[pocketcolin]

@mtrezza because since the Parse Server 8 PR, I found 2 more Mongo settings that are important. Ideally, I think 8 wouldn't validate databaseOptions because there are just too many to maintain, but I'm happy to go back and create another PR for 8 that adds the 2 new ones.

These 2 new fields are really interesting and will help people migrate to Parse 7 as well. The tldr; is that the Node Mongo driver package released a breaking change in a minor release (v6.9) that switched the autoSelectFamily default value to true while it was previously false. Parse 7 updated the Mongo version from 4 to 6.12 so people upgrading to Parse 7 are going to be impacted by this change and without the databaseOption they'll be stuck with a new configuration.

There's a discussion about this here: https://www.mongodb.com/community/forums/t/i-keep-getting-error-when-i-try-connecting-node-to-mongodb/243422/22?page=2

[mtrezza]

It would be great if you could add another PR for Parse Server 8 before we can merge this. The reason is that we aim to back-port identical code, to mitigate divergence in the branches, which would make them more difficult to maintain.

[pocketcolin]

Here you are: https://github.com/parse-community/parse-server/pull/9579/files

[mtrezza]

Looks good!

[mtrezza]

We'll merge this after Parse Server 8 release, so that it triggers a new Parse Server 7 release.

[mtrezza]

@pocketcolin Thank you for the PRs, I'll go ahead and merge this, just mind that this won't be part of a Parse Server 7 release yet. But to make it easier for you, you can just point your parse-server dependency to the commit hash on the release-7.x.x branch until a new version has been published - should be in a few days.

[parseplatformorg]

🎉 This change has been released in version 7.5.0