Get Target Pool

compute_engine.get_target_pool
ActionGoogle Cloudconnection required

Calls compute v1 GET /projects/{project}/regions/{region}/targetPools/{targetPool}.

Returns the specified target pool.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Compute Engine
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, zone
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
region
Region; defaults to the connection's zone minus its suffix.
stringNo———
target_pool
Target pool name or id.
stringYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
backupPool
string—
creationTimestamp
string—
description
string—
failoverRatio
number—
healthChecks
array—
id
string—
instances
array—
kind
string—
name
string—
region
string—
securityPolicy
string—
selfLink
string—
sessionAffinity
string—
{
  "backupPool": "",
  "creationTimestamp": "",
  "description": "",
  "failoverRatio": 0,
  "healthChecks": [],
  "id": "",
  "instances": [],
  "kind": "",
  "name": "",
  "region": "",
  "securityPolicy": "",
  "selfLink": "",
  "sessionAffinity": ""
}

See Get Target Pool run in a workflow.

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