DataDog Regional Domain Migration

Update every DataDog reference across our repos to point at the regional site
`datadoghq.eu` (change to your target site before running) instead of the default
`datadoghq.com`.

For each repository:
1. Update agent configs (`datadog.yaml`, `datadog-agent/values.yaml`):
   - Replace `site: datadoghq.com` with the target site
   - Update `dd_url`, `logs_dd_url`, `apm_dd_url`, `process_dd_url` hosts to the regional equivalents
2. Update Helm values for any chart that configures the DataDog Agent or Cluster Agent.
3. Update Terraform: `datadog` provider `api_url`, and any `dd_url`/`site` arguments
   in `datadog_*` resources.
4. Update env-var defaults in app code and Docker/K8s manifests:
   - `DD_SITE`, `DD_API_HOST`, `DD_LOG_INTAKE_URL`, `DD_TRACE_AGENT_URL`
5. Update SDK initialization in application code where the host is passed explicitly
   (`datadog.init({ site: '...' })`, `tracer.init({ ... })`, etc.).
6. Skip test fixtures and example/sample configs.

Do not modify secrets or API keys.

The Problem

When your org moves to a regional DataDog tenant (for data residency, compliance, or to consolidate billing), every agent, every Helm chart, and every SDK initialization needs to be pointed at the regional domain (e.g., `datadoghq.eu` or one of the US regional sites). Missing one means metrics and logs silently go to the wrong tenant.

The change is mechanical but spread across YAML, env-var defaults, Terraform, and application code. There’s no single grep that catches every form.

What Tidra Does

1. Searches for every reference to the default DataDog domain across YAML, Helm, Terraform, env-var defaults, and SDK init code
2. Replaces the default site with the target regional site you specify
3. Updates API host, log intake host, and trace agent host consistently
4. Skips test fixtures and ignores secrets/values files that should remain placeholder
5. Opens one PR per repo with a list of touched references

Before & After

Customization Tips

• Target region: Tell Tidra the target site (datadoghq.eu, a specific US regional site, ddog-gov.com, etc.). It will not assume.
• Multi-tenant orgs: If different teams stay on different sites, supply a team → site mapping.
• SDK init code: For SDKs that hardcode the host in initialization, Tidra updates the constructor argument as well as config.