Attach to an interactive command
A WebSocket, attached once, by the caller that created the command. Binary messages carry one channel byte and then bytes: 0 is stdin from the client, 1 stdout and 2 stderr to it. Text messages are JSON: the client sends {"type": "resize", "cols", "rows"}, {"type": "signal", "signal"} (HUP, INT, QUIT, TERM, KILL, USR1, USR2, WINCH) and {"type": "stdinClose"}; the server sends {"type": "exit", "exitCode", "signal", "code"} or {"type": "error", "code", "message"} and closes.
https://sandboxes.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/sandboxes/{sandboxId}/exec/{exec}Authorization
Path parameters
Returns
101
The WebSocket.
200
Never sent: a successful attach is 101 Switching Protocols.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.