chore(deps): Bump mongodb from 2.6.1 to 2.7.0

[dependabot]

Bumps mongodb from 2.6.1 to 2.7.0.

Release notes

Sourced from mongodb's releases.

v2.7.0

The MongoDB Rust driver team is pleased to announce the v2.7.0 release of the mongodb crate, now available for download from crates.io.

Highlighted Changes

Serialization Behavior Change

When serializing values via serde, the serializer can indicate whether or not the target format is human-readable, allowing types to change behavior based on that. The Rust driver had inadvertently been serializing values given to find_one_and_replace and replace_one as human-readible when all other methods serialize as non-human-readible; this bug is fixed in 2.7.0, with those methods also serializing as non-human-readible.

However, it is potentially possible (if unlikely) that user code may rely on this bug. If your code does rely on human-readable serialization, you can specify that via the new human_readable_serialization field in CollectionOptions.

run_cursor_command

The Rust driver provides the run_command method as a way for users to directly send bson commands to the server; this is particularly useful when the driver does not yet have support for a newly-added server command. However, using this with commands that return a cursor requires re-implementing the logic for cursor iteration, which can be tedious and error-prone. The new run_cursor_command method avoids those problems, directly returning a Cursor using the same iteration logic as other methods.

SDAM Logging

The Rust driver will now log SDAM events when using the tracing-unstable feature.

Client Management

The Client type now provides three additional ways to shape behavior to fit your workload:

• ClientOptions.max_connecting lets you specify how many "in flight" connections can be established in parallel. This was previously fixed at 2 and defaults to the same value.
• Client::warm_connection_pool will create new connections to bring the connection pool up to min_pool_size, which can provide more predictable performance in some circumstances.
• Client::shutdown will cleanly stop background tasks and wait for outstanding handles to be dropped. This is particularly useful when using event handlers that reference external resources, as otherwise those handlers may be invoked in a background task even after the Client has been dropped.

Included Changes

Below are a selected list of changes with user impact; for a full list of changes see this GitHub query.

New Features

• RUST-1420 Cache AWS credentials received from endpoints (#905)
• RUST-1604 Add custom bucketing fields to timeseries options (#907)
• RUST-1588: Add RunCursorCommand (#912)
• RUST-802 Support Unix Domain Sockets (#908) (thanks @​PureWhiteWu!)
• RUST-1509 SDAM Logging (#918)
• RUST-1608 Clean shutdown for Client (#920)
• RUST-1712 Provide a connection pool warmup method (#932)
• RUST-1712 Support User Configuration for max_connecting (#923) (thanks @​LuisOsta!)
• RUST-1687 Add human_readable_serialization option to Collection (#902) (thanks @​maiconpavi!)

Improvements

• RUST-1433 Propagate original error for some labeled retry errors (#903)
• minor: improve README.md (#934)
• upgrade webpki (#935) (thanks @​fuchsnj!)
• RUST-1763 deprecate CollectionOptions::human_readable_serialization (#957) (#959)

Bugfixes

... (truncated)

Commits

• a9e9fab release v2.7.0
• 1c36dab minor: pin async-executor (#964) (#965)
• 636de62 release v2.7.0-beta.1 (#956)
• 92b984e minor: fix deprecation warnings (#960) (#961)
• f59cef2 RUST-1763 deprecate CollectionOptions::human_readable_serialization (#957) (#...
• a8972b9 fixing the find or delete serde inconsistency (#948) (#955)
• b8446b2 RUST-1757 Fix final cursor batch handling (#951) (#954)
• 640a30a RUST-1746 Use more environment variables in Azure KMS test (#944)
• 3396d1e release v2.7.0-beta (#946)
• 2f9fe86 RUST-1539 Restructure and refine contents of Evergreen configuration (#939)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[bits-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ jszwedko
❌ dependabot[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[netlify]

✅ Deploy Preview for vector-project canceled.

Name	Link
🔨 Latest commit	b7904b8
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/651755b6466dad00070f80a3

[netlify]

✅ Deploy Preview for vrl-playground ready!

Name	Link
🔨 Latest commit	b7904b8
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/651755b6d39d690008b86ce2
😎 Deploy Preview	https://deploy-preview-18703--vrl-playground.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 site configuration.

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-18703.d1a7j77663uxsc.amplifyapp.com

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-18703.d2lr4eds605rpz.amplifyapp.com

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-18703.d1hoyoksbulg25.amplifyapp.com

[datadog-vectordotdev]

Datadog Report

Branch report: dependabot/cargo/mongodb-2.7.0
Commit report: b3d7dc0

✅ vector: 0 Failed, 0 New Flaky, 1979 Passed, 0 Skipped, 1m 17.74s Wall Time

[github-actions]

Regression Detector Results

Run ID: 5387984a-83e8-4f68-9726-6955f78339f7
Baseline: eda0378
Comparison: 539a40f
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
file_to_blackhole	egress throughput	+1.67	[+0.53, +2.82]	98.38%
syslog_log2metric_humio_metrics	ingress throughput	+1.61	[+1.47, +1.76]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+1.29	[+1.15, +1.43]	100.00%
http_text_to_http_json	ingress throughput	+1.11	[+1.00, +1.23]	100.00%
syslog_humio_logs	ingress throughput	+0.03	[-0.09, +0.14]	29.31%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	+0.01	[-0.15, +0.17]	8.65%
http_to_http_acks	ingress throughput	+0.00	[-0.14, +0.15]	3.64%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.00	[-0.16, +0.17]	1.84%
http_to_http_json	ingress throughput	+0.00	[-0.05, +0.05]	4.39%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	+0.00	[-0.14, +0.14]	0.80%
datadog_agent_remap_blackhole	ingress throughput	-0.19	[-0.30, -0.07]	99.37%
socket_to_socket_blackhole	ingress throughput	-0.19	[-0.24, -0.14]	100.00%
otlp_http_to_blackhole	ingress throughput	-0.19	[-0.37, -0.02]	93.52%
syslog_loki	ingress throughput	-0.26	[-0.33, -0.20]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	-0.36	[-0.50, -0.21]	99.99%
datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.73	[-0.89, -0.57]	100.00%
splunk_hec_route_s3	ingress throughput	-0.94	[-1.48, -0.39]	99.55%
syslog_splunk_hec_logs	ingress throughput	-1.01	[-1.08, -0.93]	100.00%
fluent_elasticsearch	ingress throughput	-1.12	[-1.43, -0.81]	100.00%
syslog_log2metric_splunk_hec_metrics	ingress throughput	-1.46	[-1.61, -1.31]	100.00%
http_to_s3	ingress throughput	-1.69	[-1.97, -1.40]	100.00%
enterprise_http_to_http	ingress throughput	-1.90	[-2.07, -1.74]	100.00%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.96	[-2.08, -1.83]	100.00%
http_to_http_noack	ingress throughput	-2.94	[-3.11, -2.78]	100.00%
syslog_regex_logs2metric_ddmetrics	ingress throughput	-3.83	[-4.28, -3.39]	100.00%