gcloud: Wed Apr 3 09:23:31 UTC 2024

gcloud/database-migration/connection-profiles/create/help

@@ -37,6 +37,9 @@ COMMANDS
      postgresql
         Create a Database Migration Service connection profile for PostgreSQL.
 
+     sqlserver
+        Create a Database Migration Service connection profile for SQL Server.
+
 NOTES
     This variant is also available:
 

gcloud/database-migration/connection-profiles/create/sqlserver

@@ -0,0 +1,106 @@
+NAME
+    gcloud database-migration connection-profiles create sqlserver - create a
+        Database Migration Service connection profile for SQL Server
+
+SYNOPSIS
+    gcloud database-migration connection-profiles create sqlserver
+        (CONNECTION_PROFILE : --region=REGION)
+        (--cloudsql-instance=CLOUDSQL_INSTANCE | [--gcs-bucket=GCS_BUCKET
+          : --gcs-prefix=GCS_PREFIX --provider=PROVIDER]) [--no-async]
+        [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    Create a Database Migration Service connection profile for SQL Server.
+
+EXAMPLES
+    To create a source connection profile my-source-profile for SQL Server:
+
+        $ gcloud database-migration connection-profiles create sqlserver \
+          my-source-profile --region=us-central1 \
+          --gcs-bucket=bucket-name --gcs-prefix=prefix/path
+
+    To create a destination connection profile my-dest-profile for SQL Server:
+
+        $ gcloud database-migration connection-profiles create sqlserver \
+          my-dest-profile --region=us-central1 \
+          --cloudsql-instance=cloudsql-id
+
+POSITIONAL ARGUMENTS
+     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.
+
+REQUIRED FLAGS
+     Exactly one of these must be specified:
+
+       --cloudsql-instance=CLOUDSQL_INSTANCE
+          If the source or destination is a Cloud SQL database, then use this
+          field to provide the respective Cloud SQL instance ID.
+
+       --gcs-bucket=GCS_BUCKET
+          Cloud Storage bucket for the source SQL Server connection profile
+          where the backups are stored.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --gcs-prefix=GCS_PREFIX
+          Cloud Storage prefix path within the bucket for the source SQL Server
+          connection profile where the backups are stored.
+
+       --provider=PROVIDER
+          Database provider, for managed databases. PROVIDER must be (only one
+          value is supported): RDS.
+
+OPTIONAL FLAGS
+     --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.
+
+     --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.
+
+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.

gcloud/database-migration/migration-jobs/create

@@ -14,6 +14,10 @@ SYNOPSIS
           : --cmek-keyring=CMEK_KEYRING --cmek-project=CMEK_PROJECT]
         [--peer-vpc=PEER_VPC | --static-ip
           | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]]
+        [--sqlserver-databases=databaseName,[...]
+          : --sqlserver-backup-file-pattern=SQLSERVER_BACKUP_FILE_PATTERN;
+          default=".(\\.|)(<epoch>\\d)\\.(trn|bak|trn\\.final)"
+          --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES]
         [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
@@ -289,6 +293,38 @@ OPTIONAL FLAGS
          --vm=VM
             Name of VM that will host the SSH tunnel bastion.
 
+     The SQL Server homogeneous migration config. This is used only for SQL
+     Server to CloudSQL SQL Server migrations.
+
+       --sqlserver-databases=databaseName,[...]
+          A list of databases to be migrated to the destination Cloud SQL
+          instance. Provide databases as a comma separated list. This list
+          should contain all encrypted and non-encrypted database names.
+
+          This flag argument must be specified if any of the other arguments in
+          this group are specified.
+
+       --sqlserver-backup-file-pattern=SQLSERVER_BACKUP_FILE_PATTERN; default=".(\\.|)(<epoch>\\d)\\.(trn|bak|trn\\.final)"
+          Pattern that describes the default backup naming strategy. The
+          specified pattern should ensure lexicographical order of backups. The
+          pattern should define the following capture group set epoch - unix
+          timestamp Example: For backup files TestDB.1691448240.bak,
+          TestDB.1691448254.trn, TestDB.1691448284.trn.final use pattern:
+          .\.(<epoch>\d)\.(trn|bak|trn\.final) or
+          .\.(<timestamp>\d)\.(trn|bak|trn\.final)
+
+       --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES
+          A JSON/YAML file describing the encryption settings per database for
+          all encrytped databases. An example of a JSON request: [{ "database":
+          "db1", "encryptionOptions": { "certPath": "Path to certificate 1",
+          "pvkPath": "Path to certificate private key 1", "pvkPassword":
+          "Private key password 1" } }, { "database": "db2",
+          "encryptionOptions": { "certPath": "Path to certificate 2",
+          "pvkPath": "Path to certificate private key 2", "pvkPassword":
+          "Private key password 2" } }]
+
+              This flag accepts "-" for stdin.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,