gcloud alpha database-migration connection-profiles create mysql - create a Database Migration Service connection profile for MySQL
gcloud alpha database-migration connection-profiles create mysql (CONNECTION_PROFILE : --region=REGION) --host=HOST --port=PORT --username=USERNAME (--password=PASSWORD | --prompt-for-password) [--no-async] [--display-name=DISPLAY_NAME] [--instance=INSTANCE] [--labels=[KEY=VALUE,...]] [--provider=PROVIDER] [--ca-certificate=CA_CERTIFICATE : --certificate=CERTIFICATE --private-key=PRIVATE_KEY] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Create a Database Migration Service connection profile for MySQL.
To create a connection profile for MySQL:
$ gcloud alpha database-migration connection-profiles create mysql \ my-profile --region=us-central1 --password=123456 \ --username=my-user --host=1.2.3.4 --port=3306
If the source is a Cloud SQL database, run:
$ gcloud alpha database-migration connection-profiles create mysql \ my-profile --region=us-central1 --password=123456 \ --username=my-user --host=1.2.3.4 --port=3306 \ --instance=my-instance --provider=CLOUDSQL
- Connection profile resource - The connection profile to create. 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 connection_profile 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.
- CONNECTION_PROFILE
ID of the connection_profile or fully qualified identifier for the connection_profile. To set the connection_profile attribute:
provide the argument connection_profile 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 connection_profile. To set the region attribute:
provide the argument connection_profile on the command line with a fully specified name;
provide the argument --region on the command line.
- --host=HOST
IP or hostname of the source database.
- --port=PORT
Network port of the source database.
- --username=USERNAME
Username that Database Migration Service uses to connect to the database. Database Migration Service encrypts the value when storing it.
- Exactly one of these must be specified:
- --password=PASSWORD
Password for the user that Database Migration Service uses to connect to the source database. Database Migration Service encrypts the value when storing it, and the field is not returned on request.
- --prompt-for-password
Prompt for the password used to connect to the database.
- --no-async
Waits for the operation in progress to complete before returning.
- --display-name=DISPLAY_NAME
A user-friendly name for the connection profile. The display name can include letters, numbers, spaces, and hyphens, and must start with a letter.
- --instance=INSTANCE
If the source is a Cloud SQL database, use this field to provide the Cloud SQL instance ID of the source.
- --labels=[KEY=VALUE,...]
List of label KEY=VALUE pairs to add.
Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers.
- --provider=PROVIDER
Database provider, for managed databases. PROVIDER must be one of: RDS, CLOUDSQL.
- --ca-certificate=CA_CERTIFICATE
x509 PEM-encoded certificate of the CA that signed the source database server's certificate. The replica will use this certificate to verify it's connecting to the correct host. Database Migration Service encrypts the value when storing it.
- --certificate=CERTIFICATE
x509 PEM-encoded certificate that will be used by the replica to authenticate against the source database server.
- --private-key=PRIVATE_KEY
Unencrypted PKCS#1 or PKCS#8 PEM-encoded private key associated with the Client Certificate. Database Migration Service encrypts the value when storing it.
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.
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. This variant is also available:
$ gcloud database-migration connection-profiles create mysql