gcloud database-migration migration-jobs restart

INFORMATION
gcloud database-migration migration-jobs restart is not available in universe domain universe.
NAME
gcloud database-migration migration-jobs restart - restart a Database Migration Service migration job
SYNOPSIS
gcloud database-migration migration-jobs restart (MIGRATION_JOB : --region=REGION) [--databases-filter=databaseName,[…]] [--endpoint-mode=ENDPOINT_MODE] [--restart-failed-objects] [--skip-validation] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
Restart a Database Migration Service migration job.
EXAMPLES
To restart a migration job: 
gcloud database-migration migration-jobs restart MIGRATION_JOB --region=us-central1
 To restart a migration job without running prior configuration verification: 
gcloud database-migration migration-jobs restart MIGRATION_JOB --region=us-central1 --skip-validation
POSITIONAL ARGUMENTS
Migration job resource - The migration job to restart. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

  • provide the argument migration_job on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

This must be specified.

MIGRATION_JOB
ID of the migration_job or fully qualified identifier for the migration_job.

To set the migration_job attribute:

  • provide the argument migration_job on the command line.

This positional argument must be specified if any of the other arguments in this group are specified.

--region=REGION
The Cloud region for the migration_job.

To set the region attribute:

  • provide the argument migration_job on the command line with a fully specified name;
  • provide the argument --region on the command line.
FLAGS
The migration job objects config.

At most one of these can be specified:

--databases-filter=databaseName,[…]
A list of databases to be migrated to the destination instance. Provide databases as a comma separated list. This flag is used only for SQL Server to Cloud SQL SQL Server migrations.
--endpoint-mode=ENDPOINT_MODE
Specifies endpoint mode for a given command. Regional endpoints provide enhanced data residency and reliability by ensuring your request is handled entirely within the specified Google Cloud region. This differs from global endpoints, which may process parts of the request outside the target region. Overrides the default regional/endpoint_mode property value for this command invocation. ENDPOINT_MODE must be one of:
global
(Default) Use global rather than regional endpoints.
regional
Only use regional endpoints. An error will be raised if a regional endpoint is not available for a given command.
regional-preferred
Use regional endpoints when available, otherwise use global endpoints. Recommended for most users.
--restart-failed-objects
Restart the failed objects in the migration job. This flag is used only for Postgres to AlloyDB, and Postgres to Cloud SQL Postgres and MySQL to Cloud SQL MySQL migrations.
--skip-validation
Restart the migration job without running prior configuration verification.
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.

REGIONAL ENDPOINTS
This command supports regional endpoints. To use regional endpoints for this command, use the --endpoint-mode=regional-preferred flag. To use regional endpoints by default, run $ gcloud config set regional/endpoint_mode regional-preferred.
NOTES
This variant is also available: 
gcloud alpha database-migration migration-jobs restart