[ABLD-310] Add --enable_bazel flag to security-agent.build

[aiuto]

What this change does

Adds an opt-in --enable-bazel flag to security-agent.build (default False).
When set, the task builds via the Bazel target //cmd/security-agent:security-agent
(using the shared build_go_binary_with_bazel helper) and copies the resulting
binary into place, instead of calling go_build(). When the flag is not set,
behavior is unchanged from today.

Also copies in the shared tasks/libs/build/bazel.py helper
(build_go_binary_with_bazel), used by the other binaries in this series.

Motivation

Omnibus deprecation.

How did you validate this

• dda inv -- -e security-agent.build --enable-bazel produces a valid Mach-O
  binary at bin/security-agent/security-agent.
• dda inv -- -e security-agent.build (legacy path, no flag) still works and
  produces the same ldflags/build_tags invocation as before.
• dda inv linter.python passes.
• bazel build //cmd/security-agent:security-agent succeeds on macOS (arm64),
  so no platform gating was needed here (unlike process-agent, which hits a
  Linux-only transitive dependency via //pkg/ebpf).

Known limitations

--enable-bazel does not support --build-tags, --race, --install-path,
--static, or --fips-mode — these raise NotImplementedError rather than
silently producing a different binary.

[github-actions]

AI review by Codex (OpenAI) - workflow run

Patch is incorrect: the Bazel path builds a target that does not apply the Agent’s standard build tags or version linker definitions.

[github-actions]

This target is still a plain rules_go go_binary, whereas the legacy path adds get_default_build_tags(...) and version ldflags. Consequently --enable-bazel can produce a materially different security-agent (including placeholder 0.0.0-dev version metadata and omitted tag-controlled features). Migrate //cmd/security-agent:security-agent to dd_agent_go_binary or otherwise provide equivalent tags/x_defs before exposing this path.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 6ec84e5e:

Results for datadog-agent_7.84.0~devel.git.556.34b7663.pipeline.133833468-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.84.0~devel.git.556.34b7663.pipeline.133833468-1_amd64.deb:

No change detected

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 90fc373b-e5bd-4366-83f9-41678683930d

Baseline: 6ec84e5
Comparison: 34b7663
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+1.58	[+0.71, +2.45]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	+1.44	[+1.20, +1.69]	1	Logs
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	+0.73	[+0.52, +0.94]	1	Logs
➖	quality_gate_security_mean_fs_load	memory utilization	+0.65	[+0.61, +0.68]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	+0.49	[+0.37, +0.61]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	+0.32	[+0.09, +0.55]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	+0.04	[+0.00, +0.07]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.01	[-0.04, +0.05]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	-0.28	[-0.36, -0.19]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.44	[-0.49, -0.39]	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	4 = 4	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	173.47MiB ≤ 179MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	747.02KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	4 = 4	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	515.97MiB ≤ 537MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.15MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	17 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	213.30MiB ≤ 220MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.48MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	356.10 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	19 ≤ 40	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	409.16MiB ≤ 455MiB	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
✅	quality_gate_private_action_runner	memory_usage	10/10	72.57MiB ≤ 75MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	28.75 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	327.26MiB ≤ 355MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	62.87 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	306.90MiB ≤ 335MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	22.27 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	306.25MiB ≤ 345MiB	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".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 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 missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, 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 total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 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 memory_usage: 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 cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_private_action_runner, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 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, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.

[dd-octo-sts]

Static quality checks

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

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	docker_agent_amd64	+18.87 KiB (0.00% increase, -2.94% of buffer)	820.372 → 820.391 → 821.000
✅	docker_agent_arm64	+10.88 KiB (0.00% increase, -1.67% of buffer)	821.345 → 821.355 → 821.980
✅	docker_agent_jmx_amd64	+18.88 KiB (0.00% increase, -2.95% of buffer)	1011.285 → 1011.303 → 1011.910
✅	docker_agent_jmx_arm64	+10.88 KiB (0.00% increase, -1.65% of buffer)	1001.037 → 1001.047 → 1001.680
✅	docker_cluster_agent_amd64	+9.21 KiB (0.00% increase, -1.01% of buffer)	211.243 → 211.252 → 212.130
✅	docker_host_profiler_amd64	+28.54 KiB (0.01% increase, -0.26% of buffer)	306.831 → 306.859 → 317.700
✅	docker_host_profiler_arm64	+20.54 KiB (0.01% increase, -0.19% of buffer)	318.144 → 318.164 → 328.970

25 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	761.368 MiB
✅	agent_deb_amd64_fips	713.895 MiB
✅	agent_heroku_amd64	312.942 MiB
✅	agent_rpm_amd64	761.352 MiB
✅	agent_rpm_amd64_fips	713.879 MiB
✅	agent_rpm_arm64	737.288 MiB
✅	agent_rpm_arm64_fips	693.118 MiB
✅	agent_suse_amd64	761.352 MiB
✅	agent_suse_amd64_fips	713.879 MiB
✅	agent_suse_arm64	737.288 MiB
✅	agent_suse_arm64_fips	693.118 MiB
✅	docker_cluster_agent_arm64	224.397 MiB
✅	docker_cws_instrumentation_amd64	7.439 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.545 MiB
✅	docker_dogstatsd_arm64	37.623 MiB
✅	dogstatsd_deb_amd64	30.286 MiB
✅	dogstatsd_deb_arm64	28.302 MiB
✅	dogstatsd_rpm_amd64	30.286 MiB
✅	dogstatsd_suse_amd64	30.286 MiB
✅	iot_agent_deb_amd64	46.560 MiB
✅	iot_agent_deb_arm64	43.196 MiB
✅	iot_agent_deb_armhf	44.003 MiB
✅	iot_agent_rpm_amd64	46.560 MiB
✅	iot_agent_suse_amd64	46.559 MiB