[pranav-new-relic]

Summary

Wires Japan as a first-class region in the newrelic-cli CI test path, mirroring the existing EU pattern.

What's added:

• .github/workflows/e2e-jp.yml — clone of e2e-eu.yml. Pulls ghcr.io/newrelic/deployer:latest, fetches test/definitions-jp/smoke from open-install-library, and runs against the JP test account via the GIT_DEPLOYER_DOCKER_USER_CONFIG_JP secret. Same trigger conditions as EU (PR + push to main).
• .github/workflows/cleanup-jp.yml — clone of cleanup-eu.yml; reaps resources after End to end testing (JP) and Release workflows.
• .github/workflows/e2e-dp-jp.yml — clone of e2e-dp-eu.yml (kept inactive, mirroring EU's currently-inactive DP variant).

The CLI's own region handling already covers JP (via newrelic-client-go's region.JP constant + the JP branch in internal/install/execution/platform_link_generator.go). No Go source changes are required for this rollout.

Prerequisites — all satisfied ✅

#	Prereq	Status
1	Deployer jp: block under newRelicUrls in src/app_config.yml	✅ Merged as deployer #32 on 2026-06-11 (originally drafted as #31, which was closed and superseded by #32).
2	ghcr.io/newrelic/deployer:latest refreshed with JP-aware image	✅ Published — verified empirically by CI provisioning EC2s in ap-northeast-1 and passing 36/36 checks.
3	OIL test/definitions-jp/smoke/ populated	✅ Merged as open-install-library #1377 on 2026-06-22 (1d9923d8 on main). 6 JP smoke test definitions present (awslinux2-infra, awslinuxarm64-infra, debian11-infra, nginx-linux2-ami, ubuntu20-infra, windows2019).
4	GitHub repo secret GIT_DEPLOYER_DOCKER_USER_CONFIG_JP	✅ Present in this repo since 2026-06-11; last updated 2026-06-16 to fix a JSON-shape issue where the secrets block needed to be nested under credentials.secrets.* (not root secrets.*) for the deployer's [credential:secrets:KEY] placeholder substitution to resolve.
5	gitdeployerCanada keypair imported into AWS ap-northeast-1	✅ Imported — verified empirically by successful JP EC2 launches in CI.

Secret JSON shape (for reference)

{
  "credentials": {
    "aws": {
      "apiKey": "<AWS access key>",
      "secretKey": "<AWS secret key>",
      "secretKeyPath": "/mnt/deployer/configs/gitdeployerCanada.pem",
      "region": "ap-northeast-1",
      "secretKeyName": "gitdeployerCanada"
    },
    "newrelic": {
      "licenseKey": "<jpx*…NRAL ingest license key>",
      "nrPersonalApiKey": "<NRAK-… JP user API key>",
      "accountId": "<JP test account ID>",
      "nrRegion": "JP",
      "nrOrganizationId": "<JP org UUID>"
    },
    "secrets": {
      "nrHostFleetId": "<JP host fleet UUID>",
      "nrWindowsHostFleetId": "<JP Windows fleet UUID>"
    }
  }
}

Verification

• CI: 36/36 checks pass on the latest push (2d9b3baf). The JP e2e workflow provisions EC2s in ap-northeast-1, runs the 6 smoke test definitions from test/definitions-jp/smoke/ against ghcr.io/newrelic/deployer:latest with the JP secret, and tears down cleanly.
• Prior runs on this branch surfaced a transient upstream Windows infra-agent install regression (US/EU/JP windows* tests all timing out identically at ==> Installing Infrastructure Agent); resolved itself between 2026-06-22 and 2026-07-06. No code changes in this PR touched the Windows install path. Context: issuecomment-4768646167.

Companion PRs

• Deployer JP region: deployer #32 — merged
• open-install-library: open-install-library #1377 — merged (tracked under NR-580447)