Authorize Environment

cloud_shell.authorize_environment
ActionGoogle Cloudconnection required

Calls Cloud Shell POST /v1/users/{usersId}/environments/{environmentsId}:authorize.

Sends OAuth credentials to a running environment on behalf of a user.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Shell
Secret shape
{"client_id", "client_secret", "refresh_token"}
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
user
Id of the user to act on, from its Cloud Shell URL or console — not its name.
stringYes———
environment
Environment id.
stringYes———
body
Request body (AuthorizeEnvironmentRequest) as JSON.
objectNo———

Output

One shape.

result

FieldTypeExample
ok
boolean—
response
object—
error
object—
name
string—
done
boolean—
metadata
object—
{
  "done": false,
  "error": {},
  "metadata": {},
  "name": "",
  "ok": false,
  "response": {}
}

Related Google Cloud Shell nodes

See Authorize Environment run in a workflow.

In a technical demo we add the Google Cloud Shell connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.