Get Target Https Proxy

compute_engine.get_target_https_proxy
ActionGoogle Cloudconnection required

Calls compute v1 GET /projects/{project}/global/targetHttpsProxies/{targetHttpsProxy}.

Returns the specified TargetHttpsProxy resource.

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

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

FieldTypeRequiredDefaultConstraintsExample
target_https_proxy
Target https proxy name or id.
stringYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
authorizationPolicy
string—
certificateMap
string—
creationTimestamp
string—
description
string—
fingerprint
string—
httpKeepAliveTimeoutSec
integer—
id
string—
kind
string—
name
string—
proxyBind
boolean—
quicOverride
string—
region
string—
selfLink
string—
serverTlsPolicy
string—
sslCertificates
array—
sslPolicy
string—
tlsEarlyData
string—
urlMap
string—
{
  "authorizationPolicy": "",
  "certificateMap": "",
  "creationTimestamp": "",
  "description": "",
  "fingerprint": "",
  "httpKeepAliveTimeoutSec": 0,
  "id": "",
  "kind": "",
  "name": "",
  "proxyBind": false,
  "quicOverride": "",
  "region": "",
  "selfLink": "",
  "serverTlsPolicy": "",
  "sslCertificates": [],
  "sslPolicy": "",
  "tlsEarlyData": "",
  "urlMap": ""
}

See Get Target Https Proxy 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.