Method: projects.locations.workflows.start

• HTTP request
• Path parameters
• Request body
• Response body
• Authorization scopes
• IAM Permissions
• Try it!

Starts a previously created migration workflow. I.e., the state transitions from DRAFT to RUNNING. This is a no-op if the state is already RUNNING. An error will be signaled if the state is anything other than DRAFT or RUNNING.

HTTP request

Choose a location:

global asia-northeast1 asia-south1 asia-south2 asia-southeast1 australia-southeast1 europe-west1 europe-west2 europe-west3 europe-west4 europe-west6 europe-west8 europe-west9 me-central2 northamerica-northeast1 northamerica-northeast2 southamerica-east1 us-central1 us-central2 us-east1 us-east4 us-east5 us-east7 us-south1 us-west1 us-west2 us-west3 us-west4 us-west8

POST https://bigquerymigration.googleapis.com/v2/{name=projects/*/locations/*/workflows/*}:start

The URLs use gRPC Transcoding syntax.

Path parameters

Parameters
name	string Required. The unique identifier for the migration workflow. Example: projects/123/locations/us/workflows/1234

Request body

The request body must be empty.

Response body

If successful, the response body is an empty JSON object.

Authorization scopes

Requires the following OAuth scope:

• https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the name resource:

• bigquerymigration.workflows.update

For more information, see the IAM documentation.