[asheth-eightfold]

Summary

Follow-up to #36. That PR dispatches EightfoldAI/vscode's sandbox.yml only for the plain sandbox label. This one does the same for the regional sandbox labels, so needs_sandbox:ap (and later :eu, :ca, …) can start and stop a CI k8s sandbox in that region.

• sandbox_k8s_request <start|stop> [region]: a region is passed as the needs_sandbox suffix (eu, ca, gov, uae, wu, ap) in the dispatch's region input.
• Every regional branch of needs_sandbox:<region> and of stop_sandbox calls it with its region.
• A region is dispatched only if it is listed in SANDBOX_K8S_REGIONS. The calling workflow (vscode's comment_actions.yml) sets it from a repo variable, space- or comma-separated. A region joins CI k8s by being listed there, with no change in this repo.
• Unchanged:
  • the plain sandbox dispatch: same payload, no region key;
  • everything when SANDBOX_K8S_TRIGGER isn't "true";
  • the labels themselves, which still go to the fleet as before.

SANDBOX_K8S_TRIGGER	SANDBOX_K8S_REGIONS	call	dispatched
true	empty	start (US)	{"pr","action":"start"}, as #36
true	empty	start ap	nothing
true	ap	start ap / stop ap	…,"region":"ap"
true	ap	start eu	nothing
true	ap,eu / ap eu	start eu	…,"region":"eu" (ca: nothing)
false	ap	any	nothing

The table was checked with the function sourced alone and curl/jq stubbed (bash -n clean).

Order

GitHub rejects a dispatch with an input the workflow doesn't define (HTTP 422; || true keeps the action green). So:

1. merge this (inert until SANDBOX_K8S_REGIONS is set);
2. merge the vscode side, which adds sandbox.yml's region input (us|ap) and passes SANDBOX_K8S_REGIONS (EightfoldAI/vscode, branch feat/asheth/eng-221179, stacked on vscode#122623);
3. set vars.SANDBOX_K8S_REGIONS=ap in vscode.

JIRA: ENG-221179

🤖 Generated with Claude Code

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None