Get Delivery Pipeline
cloud_deploy.get_delivery_pipeline
ActionGoogle Cloudconnection required
Calls Cloud Deploy GET /v1/projects/{projectsId}/locations/{locationsId}/deliveryPipelines/{deliveryPipelinesId}.
Gets details of a single DeliveryPipeline.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Deploy
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- location, project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location Location / region (overrides connection). | string | No | — | — | — |
delivery_pipeline Delivery pipeline id. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
labels | object | — |
condition | object | — |
uid | string | — |
suspended | boolean | — |
description | string | — |
updateTime | string | — |
{
"condition": {},
"description": "",
"labels": {},
"ok": false,
"suspended": false,
"uid": "",
"updateTime": ""
}See Get Delivery Pipeline run in a workflow.
In a technical demo we add the Google Cloud Deploy connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.