You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/datamigration_v1.projects.locations.migrationJobs.html
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -141,6 +141,7 @@ <h3>Method Details</h3>
141
141
The object takes the form of:
142
142
143
143
{ # Represents a Database Migration Service migration job object.
144
+
"cmekKeyName": "A String", # The CMEK (customer-managed encryption key) fully qualified key name used for the migration job. This field supports all migration jobs types except for: * Mysql to Mysql (use the cmek field in the cloudsql connection profile instead). * PostrgeSQL to PostgreSQL (use the cmek field in the cloudsql connection profile instead). * PostgreSQL to AlloyDB (use the kms_key_name field in the alloydb connection profile instead). Each Cloud CMEK key has the following format: projects/[PROJECT]/locations/[REGION]/keyRings/[RING]/cryptoKeys/[KEY_NAME]
144
145
"conversionWorkspace": { # A conversion workspace's version. # The conversion workspace used by the migration.
145
146
"commitId": "A String", # The commit ID of the conversion workspace.
146
147
"name": "A String", # The resource name (URI) of the conversion workspace.
@@ -317,6 +318,7 @@ <h3>Method Details</h3>
317
318
An object of the form:
318
319
319
320
{ # Represents a Database Migration Service migration job object.
321
+
"cmekKeyName": "A String", # The CMEK (customer-managed encryption key) fully qualified key name used for the migration job. This field supports all migration jobs types except for: * Mysql to Mysql (use the cmek field in the cloudsql connection profile instead). * PostrgeSQL to PostgreSQL (use the cmek field in the cloudsql connection profile instead). * PostgreSQL to AlloyDB (use the kms_key_name field in the alloydb connection profile instead). Each Cloud CMEK key has the following format: projects/[PROJECT]/locations/[REGION]/keyRings/[RING]/cryptoKeys/[KEY_NAME]
320
322
"conversionWorkspace": { # A conversion workspace's version. # The conversion workspace used by the migration.
321
323
"commitId": "A String", # The commit ID of the conversion workspace.
322
324
"name": "A String", # The resource name (URI) of the conversion workspace.
@@ -445,6 +447,7 @@ <h3>Method Details</h3>
445
447
{ # Response message for 'ListMigrationJobs' request.
446
448
"migrationJobs": [ # The list of migration jobs objects.
447
449
{ # Represents a Database Migration Service migration job object.
450
+
"cmekKeyName": "A String", # The CMEK (customer-managed encryption key) fully qualified key name used for the migration job. This field supports all migration jobs types except for: * Mysql to Mysql (use the cmek field in the cloudsql connection profile instead). * PostrgeSQL to PostgreSQL (use the cmek field in the cloudsql connection profile instead). * PostgreSQL to AlloyDB (use the kms_key_name field in the alloydb connection profile instead). Each Cloud CMEK key has the following format: projects/[PROJECT]/locations/[REGION]/keyRings/[RING]/cryptoKeys/[KEY_NAME]
448
451
"conversionWorkspace": { # A conversion workspace's version. # The conversion workspace used by the migration.
449
452
"commitId": "A String", # The commit ID of the conversion workspace.
450
453
"name": "A String", # The resource name (URI) of the conversion workspace.
@@ -534,6 +537,7 @@ <h3>Method Details</h3>
534
537
The object takes the form of:
535
538
536
539
{ # Represents a Database Migration Service migration job object.
540
+
"cmekKeyName": "A String", # The CMEK (customer-managed encryption key) fully qualified key name used for the migration job. This field supports all migration jobs types except for: * Mysql to Mysql (use the cmek field in the cloudsql connection profile instead). * PostrgeSQL to PostgreSQL (use the cmek field in the cloudsql connection profile instead). * PostgreSQL to AlloyDB (use the kms_key_name field in the alloydb connection profile instead). Each Cloud CMEK key has the following format: projects/[PROJECT]/locations/[REGION]/keyRings/[RING]/cryptoKeys/[KEY_NAME]
537
541
"conversionWorkspace": { # A conversion workspace's version. # The conversion workspace used by the migration.
538
542
"commitId": "A String", # The commit ID of the conversion workspace.
539
543
"name": "A String", # The resource name (URI) of the conversion workspace.
0 commit comments