Add support for MongoDBContainer credentials

[digital88]

Hopefully closes #988

This implementation supports credentials only when replica set is disabled. Because using credentials with replica set requires rather complicated setup I think it could be implemented later as separate PR. I'm not even sure why replica set was implemented in first place, as TC creates single container for running tests it does not make much sense IMO. Either way the old replica set code remains untouched and is used by default, so nothing should break for existing users.

[netlify]

✅ Deploy Preview for testcontainers-node ready!

Name	Link
🔨 Latest commit	20086b1
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-node/deploys/6880b22cb443b20008c1d6ac
😎 Deploy Preview	https://deploy-preview-1070--testcontainers-node.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[digital88]

Also very interesting that 4.0 image fails tests with:

× MongodbContainer > should connect to mongo:4.0.1 with credentials and disabled replica set 127121ms (retry x3)
     → Server at localhost:41731 reports maximum wire version 7, but this version of the Node.js Driver requires at least 8 (MongoDB 4.2)

I do not encounter this on local machine. Need to investigate more.

[digital88]

Ok, I decided to start from scratch here. I wrote a new mongodb-container-2.ts file with mongo container implementation. This version works for replica set both with and without auth. Mongo 5.0 and later is supported. Earlier images unfortunately don't work because of old mongo shell.
The main problem that I encountered was that mongo is doing some stuff in background after container is started and this causes eval commands to fail with Authentication failed errors. If I wait a little on breakpoint, tests suddenly start passing without errors. So I made basic retries logic in executeMongoEvalCommand and it actually solved this random errors I got earlier.
Edit: I'll try to port old code to this 'new' implementation.

[digital88]

Also very interesting that 4.0 image fails tests with:

Had to pin mongoose to "8.15.0". Newer versions do not support mongo 4.

I moved all logic in containerStarted to healthcheck and changed wait strategy to wait for healthcheck. Took inspiration from searching how to run mongo replica set with auth in compose. Not sure about default timeouts tho.

Credentials work with images from 4.0.1 up to 8.0

[digital88]

Tests with podman fail healthcheck even in older cases without credentials. I think my timeouts may be the reason? I have only docker installed locally. Will try later to test in podman too.

[digital88]

Changed CMD to CMD-SHELL as used in other modules. Tests pass in podman locally.

[cristianrgreco]

@digital88 do you mind resolving the conflicts? I would but I’m afk at the moment. Should just be a testcontainers version bump

[digital88]

@digital88 do you mind resolving the conflicts? I would but I’m afk at the moment. Should just be a testcontainers version bump

Resolved

[digital88]

@digital88 do you mind resolving the conflicts? I would but I’m afk at the moment. Should just be a testcontainers version bump

Resolved

And resolved again 😄

[cristianrgreco]

Apologies @digital88, things are a bit busy at the moment, I know I need to review this PR, I will get to it soon.

[cristianrgreco]

Had to pin mongoose to "8.15.0". Newer versions do not support mongo 4.

Let's not pin the mongoose version. It's pinned because of a Mongo version which was EOL Feb 2024, so when we need to update mongoose for some other reason we'll be stuck. As this is a new behaviour we don't need to test it with older Mongo versions as there are no existing users using it, so let's remove the credentials test for Mongo 4. The existing Mongo 4 test continues to pass so that's good enough from my perspective that this isn't a breaking change. If a user wants to use an older version of Mongoose so that it works with their Mongo 4 then great, but let's not tie ourselves to it.

[digital88]

Had to pin mongoose to "8.15.0". Newer versions do not support mongo 4.

Let's not pin the mongoose version. It's pinned because of a Mongo version which was EOL Feb 2024, so when we need to update mongoose for some other reason we'll be stuck. As this is a new behaviour we don't need to test it with older Mongo versions as there are no existing users using it, so let's remove the credentials test for Mongo 4. The existing Mongo 4 test continues to pass so that's good enough from my perspective that this isn't a breaking change. If a user wants to use an older version of Mongoose so that it works with their Mongo 4 then great, but let's not tie ourselves to it.

I unpinned mongoose. Made tests with creds to run just on mongo 8.0

[digital88]

Oh, sorry, TC patch version just went up again...Will fix it in a minute.

[digital88]

Looks like I messed lockfile..I'll fix it.

[cristianrgreco]

@digital88 Are there any more changes you'd like to make?

[digital88]

@digital88 Are there any more changes you'd like to make?

I think it's good 👍

[cristianrgreco]

Thanks for the contribution, always a pleasure!