gcloud: Wed Feb 12 10:41:39 UTC 2025

gcloud/dataflow/flex-template/build

@@ -11,6 +11,7 @@ SYNOPSIS
           | --jar=[JAR,...] | --py-path=[PY_PATH,...]))
         [--additional-experiments=[ADDITIONAL_EXPERIMENTS,...]]
         [--additional-user-labels=[ADDITIONAL_USER_LABELS,...]]
+        [--cloud-build-service-account=CLOUD_BUILD_SERVICE_ACCOUNT]
         [--dataflow-kms-key=DATAFLOW_KMS_KEY] [--disable-public-ips]
         [--enable-streaming-engine] [--gcs-log-dir=GCS_LOG_DIR]
         [--image-repository-cert-path=IMAGE_REPOSITORY_CERT_PATH]
@@ -131,6 +132,18 @@ OPTIONAL FLAGS
      --additional-user-labels=[ADDITIONAL_USER_LABELS,...]
         Default user labels to pass to the job.
 
+     --cloud-build-service-account=CLOUD_BUILD_SERVICE_ACCOUNT
+        Service account to run the Cloud Build in the format
+        projects/{project}/serviceAccounts/{service_account}. Ensure that the
+        account you are using to run 'gcloud dataflow flex-template build' has
+        'ServiceAccountUser' role on the specified Cloud Build service account
+        you provide with the --cloud-build-service-account flag. The specified
+        service account must have required permissions to build the image. If
+        the specified service account is in a project that is different from
+        the project where you are starting builds, see
+        https://cloud.google.com/build/docs/securing-builds/configure-user-specified-service-accounts#cross-project_set_up
+        to grant the necessary access.
+
      --dataflow-kms-key=DATAFLOW_KMS_KEY
         Default Cloud KMS key to protect the job resources.