CLOUD-727: Bump go.mongodb.org/mongo-driver from 1.11.4 to 1.12.1

[dependabot]

Bumps go.mongodb.org/mongo-driver from 1.11.4 to 1.12.1.

Release notes

Sourced from go.mongodb.org/mongo-driver's releases.

MongoDB Go Driver 1.12.1

The MongoDB Go Driver Team is pleased to release version 1.12.1 of the official Go driver.

Release Notes

This release fixes a bug in the Go Driver where connections are leaked if a user runs a transaction while connected to a load balancer. To resolve this issue, the Go Driver will now unpin connections when ending a session.

This release fixes a logging design oversight in which enabling logging with options.LogComponentAll does not result in the publication of logs.

This release fixes two runtime errors, which occur on unmarshaling an empty bson.RawValue with an invalid type, specifically the 0x00 (null) type, and on marshaling a nil pointer of ReadConcern.

---

For a full list of tickets included in this release, please see the links below:

• Improvements

• Bugs

• Tasks

Full Changelog: v1.12.0...v1.12.1

Documentation for the Go driver can be found on pkg.go.dev and the MongoDB documentation site. BSON library documentation is also available on pkg.go.dev. Questions and inquiries can be asked on the MongoDB Developer Community. Bugs can be reported in the Go Driver project in the MongoDB JIRA where a list of current issues can be found. Your feedback on the Go driver is greatly appreciated!

MongoDB Go Driver 1.12.0

The MongoDB Go Driver Team is pleased to release version 1.12.0 of the official Go driver.

Release Notes

This release adds support for MongoDB 7.0, including production-ready support for Queryable Encryption. It also adds a new logging interface and configuration API improvements.

Production-Ready Queryable Encryption

This release introduces backwards breaking changes to the Queryable Encryption protocol. Using Queryable Encryption now requires MongoDB 7.0+ and libmongocrypt v1.8.0+.

It also adds the new ClientEncryption.CreateEncryptedCollection method to automatically create data encryption keys when creating a new encrypted collection and adds the ability to fetch KMS credentials automatically from Azure, GCP, and AWS environments.

Logging

This release introduces a logging interface to allow users to more easily record detailed information about connection management and command execution within their application.

The logging configuration adds a new LogSink interface that is compatible with the logr.LogSink interface, allowing users to use existing logr adapters, like zerologr or zapr. Users may also implement their own LogSink adapter.

For example, to integrate logging with an existing zerolog logger:

sink := zerologr.New(&myLogger).GetSink()
loggerOptions := options.Logger().SetSink(sink)
options.Client().SetLoggerOptions(loggerOptions)

... (truncated)

Commits

• c8bbc62 Update version to v1.12.1
• 3ff68c3 GODRIVER-2930 Allow setting batch size for subsequent getMore's on a ChangeSt...
• 730e825 Merge branch 'release/1.12' of github.com:mongodb/mongo-go-driver into releas...
• f14bd3a Add 1.11.8 retract directive (#1341)
• d219098 GODRIVER-2881 Enable logging for ComponentAll (#1340)
• afb5419 GODRIVER-2891 Add documentation for log levels (#1312)
• 8857a04 GODRIVER-2887 Remove use of reflect.Value.MethodByName in bson (#1308)
• 9318bc2 GODRIVER-2869 Test touchup (#1307)
• 436a982 GODRIVER-2869 Two protocol validations to reduce client denial of service ris...
• 989b3e1 GODRIVER-2851 Fix failing "TestCMAPProse" test. (#1316)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

The base commit for this pull request has not changed.

[JNKPercona]

Test name	Status
arbiter	passed
cross-site-sharded	passed
data-at-rest-encryption	passed
data-sharded	passed
demand-backup	passed
demand-backup-eks-credentials	passed
demand-backup-physical	passed
demand-backup-physical-sharded	passed
demand-backup-sharded	passed
expose-sharded	passed
ignore-labels-annotations	passed
init-deploy	passed
limits	passed
liveness	passed
mongod-major-upgrade	passed
mongod-major-upgrade-sharded	passed
monitoring-2-0	passed
multi-cluster-service	failure
non-voting	passed
one-pod	passed
operator-self-healing-chaos	passed
pitr	passed
pitr-sharded	passed
recover-no-primary	passed
rs-shard-migration	passed
scaling	passed
scheduled-backup	passed
security-context	passed
self-healing-chaos	passed
service-per-pod	passed
serviceless-external-nodes	passed
smart-update	passed
storage	passed
upgrade	passed
upgrade-consistency	passed
upgrade-sharded	passed
users	passed
version-service	passed
We run 38 out of 38

commit: d4dad81
image: perconalab/percona-server-mongodb-operator:PR-1283-d4dad817