Update Workload

assured_workloads.update_workload
ActionGoogle Cloudconnection required

Calls assuredworkloads v1 PATCH /v1/organizations/{organizationsId}/locations/{locationsId}/workloads/{workloadsId}.

Updates an existing workload.

Connection

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

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
organization
Organization name or id.
stringYes———
location
Location or region; taken from the connection when unset.
stringNo———
workload
Workload name or id.
stringYes———
body
The GoogleCloudAssuredworkloadsV1Workload resource, as the API defines it.
objectYes———
update_mask
The list of fields to be updated. Optional.
stringNo———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
billingAccount
string—
complianceRegime
string—
complianceStatus
object—
compliantButDisallowedServices
array—
createTime
string—
displayName
string—
ekmProvisioningResponse
object—
enableSovereignControls
boolean—
etag
string—
kajEnrollmentState
string—
kmsSettings
object—
labels
object—
name
string—
partner
string—
partnerPermissions
object—
partnerServicesBillingAccount
string—
provisionedResourcesParent
string—
resourceMonitoringEnabled
boolean—
resourceSettings
array—
resources
array—
saaEnrollmentResponse
object—
violationNotificationsEnabled
boolean—
workloadOptions
object—
{
  "billingAccount": "",
  "complianceRegime": "",
  "complianceStatus": {},
  "compliantButDisallowedServices": [],
  "createTime": "",
  "displayName": "",
  "ekmProvisioningResponse": {},
  "enableSovereignControls": false,
  "etag": "",
  "kajEnrollmentState": "",
  "kmsSettings": {},
  "labels": {},
  "name": "",
  "partner": "",
  "partnerPermissions": {},
  "partnerServicesBillingAccount": "",
  "provisionedResourcesParent": "",
  "resourceMonitoringEnabled": false,
  "resourceSettings": [],
  "resources": [],
  "saaEnrollmentResponse": {},
  "violationNotificationsEnabled": false,
  "workloadOptions": {}
}

See Update Workload run in a workflow.

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