Update module github.com/hashicorp/consul/api to v1.34.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/hashicorp/consul/api	v1.32.1 → v1.34.3

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dd-prapprover]

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

• ✅ PR is eligible for auto-approval by rule datadog-agent-renovate - 2026-06-04T23:05:28Z
• ⬜ CI tests passed
• ⬜ Approved
• Manual merge required: this rule does not auto-merge.

➡️ Current phase: CI tests failed. Please fix the failing tests to continue.

[datadog-prod-us1-6]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/datadog-agent | oracle: [21.3.0-xe]     

See error

Failed to ping oracle instance: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

ℹ️ Info

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 50.60% (-0.00%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e0ff336 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

Go Package Import Differences

Baseline: 5d56c6c
Comparison: e0ff336

binary	os	arch	change
agent	linux	amd64	+0, -1 -github.com/mitchellh/mapstructure
agent	linux	arm64	+0, -1 -github.com/mitchellh/mapstructure
agent	windows	amd64	+0, -1 -github.com/mitchellh/mapstructure
agent	darwin	amd64	+0, -1 -github.com/mitchellh/mapstructure
agent	darwin	arm64	+0, -1 -github.com/mitchellh/mapstructure
agent	aix	ppc64	+0, -1 -github.com/mitchellh/mapstructure
heroku-agent	linux	amd64	+0, -1 -github.com/mitchellh/mapstructure
otel-agent	linux	amd64	+0, -1 -github.com/mitchellh/mapstructure
otel-agent	linux	arm64	+0, -1 -github.com/mitchellh/mapstructure
host-profiler	linux	amd64	+0, -1 -github.com/mitchellh/mapstructure
host-profiler	linux	arm64	+0, -1 -github.com/mitchellh/mapstructure

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 5d56c6ca:

Results for datadog-agent_7.81.0~devel.git.542.e0ff336.pipeline.117214861-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 5d56c6c
📊 Static Quality Gates Dashboard
🔗 SQG Job

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	docker_host_profiler_amd64	-102.08 KiB (0.03% reduction, +0.76% of buffer)	304.601 → 304.501 → 317.640
✅	docker_host_profiler_arm64	-93.2 KiB (0.03% reduction, +0.69% of buffer)	315.725 → 315.634 → 328.900

30 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	753.323 MiB
✅	agent_deb_amd64_fips	709.106 MiB
✅	agent_heroku_amd64	312.146 MiB
✅	agent_rpm_amd64	753.307 MiB
✅	agent_rpm_amd64_fips	709.090 MiB
✅	agent_rpm_arm64	728.619 MiB
✅	agent_rpm_arm64_fips	688.145 MiB
✅	agent_suse_amd64	753.307 MiB
✅	agent_suse_amd64_fips	709.090 MiB
✅	agent_suse_arm64	728.619 MiB
✅	agent_suse_arm64_fips	688.145 MiB
✅	docker_agent_amd64	812.880 MiB
✅	docker_agent_arm64	813.216 MiB
✅	docker_agent_jmx_amd64	1003.821 MiB
✅	docker_agent_jmx_arm64	992.809 MiB
✅	docker_cluster_agent_amd64	209.734 MiB
✅	docker_cluster_agent_arm64	222.847 MiB
✅	docker_cws_instrumentation_amd64	7.447 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.829 MiB
✅	docker_dogstatsd_arm64	37.883 MiB
✅	dogstatsd_deb_amd64	30.490 MiB
✅	dogstatsd_deb_arm64	28.487 MiB
✅	dogstatsd_rpm_amd64	30.490 MiB
✅	dogstatsd_suse_amd64	30.490 MiB
✅	iot_agent_deb_amd64	45.596 MiB
✅	iot_agent_deb_arm64	42.315 MiB
✅	iot_agent_deb_armhf	43.109 MiB
✅	iot_agent_rpm_amd64	45.596 MiB
✅	iot_agent_suse_amd64	45.595 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: fec1cc38-b852-4354-b80f-5105b5adc857

Baseline: 7305cd1
Comparison: 3eae816
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_idle	memory utilization	+0.45	[+0.39, +0.50]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.22	[-0.26, -0.18]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-0.59	[-0.82, -0.35]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-0.89	[-1.93, +0.15]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	quality_gate_idle	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	145.87MiB ≤ 147MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	727.88KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	3 ≤ 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	477.21MiB ≤ 495MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.12MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	180.11MiB ≤ 195MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.40MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	346.16 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	4 ≤ 6	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	379.74MiB ≤ 430MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.94GiB ≤ 1.04GiB	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Profiling Replicate Execution Failures (ddprof)

Note: Profiling replicas may still be executing. See the debug dashboard for up to date status.

Experiment	Variant	Replicates	Failure	Debug Dashboard
quality_gate_idle_all_features	baseline	10	Oom killed	Debug Dashboard
quality_gate_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_logs	comparison	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	baseline	10	Oom killed	Debug Dashboard
quality_gate_metrics_logs	comparison	10	Oom killed	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-05 06:45:45 UTC ℹ️ Start processing command /merge

---

2026-06-05 06:45:49 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 4h (p90).

---

2026-06-05 07:36:24 UTC ℹ️ MergeQueue: This merge request was merged