@W-19159693@: mongo driver update

[anayabuSF]

GUS: W-19159693

The previous version of mongodb_exporter was built with an outdated Go MongoDB driver that had a TLS handling limitation. Specifically, it was only reading the first certificate in the CA chain file, assuming it to be the issuer of the server certificate. This caused TLS validation failures when the server certificate was issued by an intermediate CA instead of the first certificate in the file.

To fix this, we upgraded mongodb_exporter to use go.mongodb.org/mongo-driver v1.8.6, which correctly processes full CA chains. With this update, the exporter can validate certificates issued by intermediate CAs, ensuring successful TLS/X.509 connections and reliable metric collection.

[ispringer]

minor: but I prefer naming a branch like this v0.11.2-evg, and name the tags cut off that branch evg1, evg2, etc. Not a big deal though. We can always rename the branch later if/when we have another patch

[anayabuSF]

Not sure why it did not dismiss review on pushing commit.

go version fixed:

/opt/mongodb_exporter/mongodb_exporter --version
mongodb_exporter, version 0.11.2-evg1 (branch: remotes/origin/ops/W-19159693-update-mongo-driver, revision: 8bb62b6391a886304daa270af6c260868a67bd1d)
  build user:       [email protected]
  build date:       20250729-21:15:59
  go version:       go1.24.2

And then make file make both binaries for us on running make release-multi-arch

anayabu-ltm28hm:mongodb_exporter anayabu$ ls -al bin/
total 20864
drwxr-xr-x  6 anayabu staff      192 Jul 29 14:16 .
drwxr-xr-x 33 anayabu staff     1056 Jul 29 14:28 ..
drwxr-xr-x  3 anayabu staff       96 Jul 29 14:16 mongodb_exporter-0.11.2-evg1.linux-aarch64
-rw-r--r--  1 anayabu staff 10288788 Jul 29 14:16 mongodb_exporter-0.11.2-evg1.linux-aarch64.tar.gz
drwxr-xr-x  3 anayabu staff       96 Jul 29 14:16 mongodb_exporter-0.11.2-evg1.linux-amd64
-rw-r--r--  1 anayabu staff 11074095 Jul 29 14:16 mongodb_exporter-0.11.2-evg1.linux-amd64.tar.gz

[johnwatts]

Not sure why it did not dismiss review on pushing commit.

Branch protection rules have to be set on each repository individually and none of this stuff is on by default. Similarly, zero reviews are required to merge in this repository. We should follow the written policy (same as evergage-product) but since these repos are almost never modified and there are many it probably isn't worth creating the rules.