Analyze Workload Move

assured_workloads.analyze_workload_move
ActionGoogle Cloudconnection required

Calls Assured Workloads GET /v1/organizations/{organizationsId}/locations/{locationsId}/workloads/{workloadsId}:analyzeWorkloadMove.

Analyzes a hypothetical move of a source resource to a target workload to surface compliance risks. The analysis is best effort and is not guaranteed to be exhaustive.

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
location, project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
location
Location / region (overrides connection).
stringNo———
organization
Organization id.
stringYes———
workload
Id of the workload to act on, from assured_workloads.list_workloads — not its name.
stringYes———
asset_types
Optional. List of asset types to be analyzed, including and under the source resource. If empty, all assets ar
stringNo———
page_size
Optional. Page size. If a value is not specified, the default value of 10 is used. The maximum value is 50.
numberNo50≥ 1—
page_token
Optional. The page token from the previous response. It needs to be passed in the second and following request
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "page_size": 50
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
nextPageToken
string—
assetMoveAnalyses
array—
{
  "assetMoveAnalyses": [],
  "nextPageToken": "",
  "ok": false
}

See Analyze Workload Move 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.