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/storagetransfer_v1.transferJobs.html
+24Lines changed: 24 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -240,6 +240,10 @@ <h3>Method Details</h3>
240
240
},
241
241
"container": "A String", # Required. The container to transfer from the Azure Storage account.
242
242
"credentialsSecret": "A String", # Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { "sas_token" : "SAS_TOKEN" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`
243
+
"federatedIdentityConfig": { # Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac) # Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret.
244
+
"clientId": "A String", # Required. Client (application) ID of the application with federated credentials.
245
+
"tenantId": "A String", # Required. Tenant (directory) ID of the application with federated credentials.
246
+
},
243
247
"path": "A String", # Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.
244
248
"storageAccount": "A String", # Required. The name of the Azure Storage account.
245
249
},
@@ -443,6 +447,10 @@ <h3>Method Details</h3>
443
447
},
444
448
"container": "A String", # Required. The container to transfer from the Azure Storage account.
445
449
"credentialsSecret": "A String", # Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { "sas_token" : "SAS_TOKEN" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`
450
+
"federatedIdentityConfig": { # Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac) # Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret.
451
+
"clientId": "A String", # Required. Client (application) ID of the application with federated credentials.
452
+
"tenantId": "A String", # Required. Tenant (directory) ID of the application with federated credentials.
453
+
},
446
454
"path": "A String", # Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.
447
455
"storageAccount": "A String", # Required. The name of the Azure Storage account.
448
456
},
@@ -673,6 +681,10 @@ <h3>Method Details</h3>
673
681
},
674
682
"container": "A String", # Required. The container to transfer from the Azure Storage account.
675
683
"credentialsSecret": "A String", # Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { "sas_token" : "SAS_TOKEN" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`
684
+
"federatedIdentityConfig": { # Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac) # Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret.
685
+
"clientId": "A String", # Required. Client (application) ID of the application with federated credentials.
686
+
"tenantId": "A String", # Required. Tenant (directory) ID of the application with federated credentials.
687
+
},
676
688
"path": "A String", # Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.
677
689
"storageAccount": "A String", # Required. The name of the Azure Storage account.
678
690
},
@@ -888,6 +900,10 @@ <h3>Method Details</h3>
888
900
},
889
901
"container": "A String", # Required. The container to transfer from the Azure Storage account.
890
902
"credentialsSecret": "A String", # Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { "sas_token" : "SAS_TOKEN" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`
903
+
"federatedIdentityConfig": { # Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac) # Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret.
904
+
"clientId": "A String", # Required. Client (application) ID of the application with federated credentials.
905
+
"tenantId": "A String", # Required. Tenant (directory) ID of the application with federated credentials.
906
+
},
891
907
"path": "A String", # Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.
892
908
"storageAccount": "A String", # Required. The name of the Azure Storage account.
893
909
},
@@ -1111,6 +1127,10 @@ <h3>Method Details</h3>
1111
1127
},
1112
1128
"container": "A String", # Required. The container to transfer from the Azure Storage account.
1113
1129
"credentialsSecret": "A String", # Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { "sas_token" : "SAS_TOKEN" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`
1130
+
"federatedIdentityConfig": { # Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac) # Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret.
1131
+
"clientId": "A String", # Required. Client (application) ID of the application with federated credentials.
1132
+
"tenantId": "A String", # Required. Tenant (directory) ID of the application with federated credentials.
1133
+
},
1114
1134
"path": "A String", # Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.
1115
1135
"storageAccount": "A String", # Required. The name of the Azure Storage account.
1116
1136
},
@@ -1316,6 +1336,10 @@ <h3>Method Details</h3>
1316
1336
},
1317
1337
"container": "A String", # Required. The container to transfer from the Azure Storage account.
1318
1338
"credentialsSecret": "A String", # Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { "sas_token" : "SAS_TOKEN" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`
1339
+
"federatedIdentityConfig": { # Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac) # Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret.
1340
+
"clientId": "A String", # Required. Client (application) ID of the application with federated credentials.
1341
+
"tenantId": "A String", # Required. Tenant (directory) ID of the application with federated credentials.
1342
+
},
1319
1343
"path": "A String", # Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.
1320
1344
"storageAccount": "A String", # Required. The name of the Azure Storage account.
"description": "Optional. The Resource name of a secret in Secret Manager. The Azure SAS token must be stored in Secret Manager in JSON format: { \"sas_token\" : \"SAS_TOKEN\" } GoogleServiceAccount must be granted `roles/secretmanager.secretAccessor` for the resource. See [Configure access to a source: Microsoft Azure Blob Storage] (https://cloud.google.com/storage-transfer/docs/source-microsoft-azure#secret_manager) for more information. If `credentials_secret` is specified, do not specify azure_credentials. Format: `projects/{project_number}/secrets/{secret_name}`",
765
765
"type": "string"
766
766
},
767
+
"federatedIdentityConfig": {
768
+
"$ref": "FederatedIdentityConfig",
769
+
"description": "Optional. Federated identity config of a user registered Azure application. If `federated_identity_config` is specified, do not specify azure_credentials or credentials_secret."
770
+
},
767
771
"path": {
768
772
"description": "Root path to transfer objects. Must be an empty string or full path name that ends with a '/'. This field is treated as an object prefix. As such, it should generally not begin with a '/'.",
769
773
"type": "string"
@@ -932,6 +936,21 @@
932
936
},
933
937
"type": "object"
934
938
},
939
+
"FederatedIdentityConfig": {
940
+
"description": "Identities of a user registered Azure application that enables identity federation to trust tokens issued by the user's Google service account. For more information about Azure application and identity federation, see [Register an application with the Microsoft identity platform] (https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) Azure RBAC roles then need be assigned to the Azure application to authorize access to the user's Azure data source. For more information about Azure RBAC roles for blobs, see [Manage Access Rights with RBAC] (https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-azure-active-directory#manage-access-rights-with-rbac)",
941
+
"id": "FederatedIdentityConfig",
942
+
"properties": {
943
+
"clientId": {
944
+
"description": "Required. Client (application) ID of the application with federated credentials.",
945
+
"type": "string"
946
+
},
947
+
"tenantId": {
948
+
"description": "Required. Tenant (directory) ID of the application with federated credentials.",
949
+
"type": "string"
950
+
}
951
+
},
952
+
"type": "object"
953
+
},
935
954
"GcsData": {
936
955
"description": "In a GcsData resource, an object's name is the Cloud Storage object's name and its \"last modification time\" refers to the object's `updated` property of Cloud Storage objects, which changes when the content or the metadata of the object is updated.",
0 commit comments