Skip to content

exec

whzbox exec <provider> [-- cmd args...] runs a child process with sandbox environment variables injected.

Syntax

whzbox exec <provider> [-- cmd args...]
whzbox exec <provider> -s "<shell command>"
whzbox exec <provider>

Arguments

Argument Required Values Description
provider Yes aws, azure, gcp Sandbox provider kind. Azure and GCP are accepted only to return the console-only error.
cmd args... No Any child argv Command to run. Omit it to launch a subshell.

Flags

Flag Type Default Description
-s, --shell boolean false Treats the single command argument as a shell string and runs /bin/sh -c.

Behavior

  • Reads the cached sandbox directly from the local store.
  • Does not refresh tokens.
  • Does not prompt for credentials.
  • Rejects unknown providers.
  • Rejects azure and gcp with an actionable error because Whizlabs does not return a workload identity or other programmatic credential for them.
  • Rejects expired or missing cached sandboxes.
  • Appends provider-specific environment variables to the current process environment.
  • Propagates the child process exit code.

Environment variables injected for AWS

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY
  • AWS_REGION
  • AWS_DEFAULT_REGION

Output

whzbox exec does not wrap child output. The child process writes directly to the inherited stdout and stderr streams.

Exit behavior

  • 0 when the child process exits successfully
  • child exit code when the child process exits non-zero
  • 1 for local execution errors, invalid shell usage, or missing cached sandbox

whzbox exec azure and whzbox exec gcp also exit 1 and explain that the sandbox is browser-console only.

See also