Patch Profile

cloud_profiler.patch_profile
ActionGoogle Cloudconnection required

Calls Cloud Profiler PATCH /v2/projects/{projectsId}/profiles/{profilesId}.

UpdateProfile updates the profile bytes and labels on the profile resource created in the online mode.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
profile
Id of the profile to act on, from cloud_profiler.list_profiles — not its name.
stringYes———
update_mask
Field mask used to specify the fields to be overwritten. Currently only profile_bytes and labels fields are su
stringNo———
body
Request body (Profile) as JSON.
objectYes———

Output

One shape.

result

FieldTypeExample
ok
boolean—
name
string—
startTime
string—
profileBytes
string—
deployment
object—
labels
object—
profileType
string—
{
  "deployment": {},
  "labels": {},
  "name": "",
  "ok": false,
  "profileBytes": "",
  "profileType": "",
  "startTime": ""
}

Related Google Cloud Profiler nodes

See Patch Profile run in a workflow.

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