TalosError: Missing required environment variable MOZILLA_OFFICIAL when running integration tests

Short answer

No — Talos should not auto-generate a temporary API key for local runs. For your immediate goal (run the suite locally with no external credentials), set MOZILLA_OFFICIAL for the test invocation only and leave MOZ_API_KEY unset. Talos will print WARNING: No MOZ_API_KEY set; results will not be uploaded. and continue, which is exactly the behavior you want.

The fix for your case

Scope the variable to the single command rather than exporting it globally, because MOZILLA_OFFICIAL is a build/harness flag used across Mozilla tooling and can change behavior outside Talos:

MOZILLA_OFFICIAL=1 ./mach talos-test --suite <your-suite>
# or, for direct invocation:
MOZILLA_OFFICIAL=1 python talos/run_tests.py <config>

Verify the run completes, that only the no-upload warning appears, and that local result files (JSON output) are written. Also confirm nothing from the run shows up in the production performance dashboard — that proves upload was genuinely skipped.

Likely explanation vs. confirmed facts

Confirmed from your description: the harness hard-fails when MOZILLA_OFFICIAL is unset, but only warns when MOZ_API_KEY is missing. The likely explanation — not confirmed without reading your tree — is that the MOZILLA_OFFICIAL check runs before the upload path is gated, so an unset flag aborts execution even though the upload it guards would have been skipped anyway. That ordering is arguably a harness bug, which matches the TODO comment you found. Exact behavior varies by Talos version and by whether you invoke via mach, mozharness, or directly, so check the source in your checkout to see where the variable is read and whether a --no-upload or local-results option already exists.

Why auto-generating a key is the wrong direction

• Security and audit: a local harness minting credentials for an external service creates revocation, scoping, and audit-trail problems, and couples every local run to the upload service's availability.
• Data pollution: downstream consumers — dashboards, perf comparison tools, alerting — expect uploaded data to mean something. Local runs uploaded under throwaway keys would contaminate production series unless every consumer filters them.

If ephemeral keys were ever implemented despite this, they would need to be scoped to a single run and a non-production results bucket, held only in process memory or a temp file with restrictive permissions, and revoked in a finally-style cleanup hook. That is a lot of machinery to solve a problem that doesn't exist.

The better design

An explicit local mode — a --no-upload flag, or treating MOZILLA_OFFICIAL=0 as "skip the credential requirement and the upload entirely" — removes the inconsistency across branches without inventing credentials. Results go only to local files, the TODO resolves itself, and downstream processes are unaffected because nothing is uploaded. If you can share the Talos version and how you invoke it (mach vs. direct), the recommendation on whether to patch the gate or just set the variable can be made more specific.