gcloud: Wed Mar 12 10:54:38 UTC 2025

gcloud/alpha/bq/migration-workflows/create

@@ -0,0 +1,43 @@
+NAME
+    gcloud alpha bq migration-workflows create - create migrationWorkflows
+
+SYNOPSIS
+    gcloud alpha bq migration-workflows create --config-file=CONFIG_FILE
+        --location=LOCATION [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Create a migrationWorkflow
+
+EXAMPLES
+    To create a migration workflow in US synchronously based on a config file,
+    run:
+
+        $ gcloud alpha bq migration-workflows create --location=US \
+            --config-file=config_file.yaml --no-async
+
+REQUIRED FLAGS
+     --config-file=CONFIG_FILE
+        The path to the migration workflows config file.
+
+     --location=LOCATION
+        The location of the migration workflow.
+
+OPTIONAL FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/bq/migration-workflows/help

@@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS
 COMMANDS
     COMMAND is one of the following:
 
+     create
+        (ALPHA) create migrationWorkflows.
+
      delete
         (ALPHA) Delete migrationWorkflows.