Update Migration Job
database_migration.update_migration_job
ActionGoogle Cloudconnection required
Calls datamigration v1 PATCH /v1/projects/{projectsId}/locations/{locationsId}/migrationJobs/{migrationJobsId}.
Updates the parameters of a single migration job.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Database Migration
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- 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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
location Location or region; taken from the connection when unset. | string | No | — | — | — |
migration_job Migration job name or id. | string | Yes | — | — | — |
body The MigrationJob resource, as the API defines it. | object | Yes | — | — | — |
update_mask Field mask is used to specify the fields to be overwritten by the update in the conversion workspace resource. Optional. | string | No | — | — | — |
Output
One shape.
result
Extra keys beyond the ones listed can appear.
| Field | Type | Example |
|---|---|---|
done | boolean | — |
error | object | — |
metadata | object | — |
name | string | — |
response | object | — |
{
"done": false,
"error": {},
"metadata": {},
"name": "",
"response": {}
}See Update Migration Job run in a workflow.
In a technical demo we add the Google Database Migration connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.