feat(cloudfunctions): update the api

#### cloudfunctions:v1

The following keys were added:
- schemas.CloudFunction.properties.buildServiceAccount.type (Total Keys: 1)

#### cloudfunctions:v2

The following keys were added:
- resources.projects.resources.locations.resources.functions.methods.abortFunctionUpgrade (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.commitFunctionUpgrade (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.redirectFunctionUpgradeTraffic (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.rollbackFunctionUpgradeTraffic (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.setupFunctionUpgradeConfig (Total Keys: 12)
- schemas.AbortFunctionUpgradeRequest (Total Keys: 2)
- schemas.CommitFunctionUpgradeRequest (Total Keys: 2)
- schemas.Function.properties.createTime (Total Keys: 3)
- schemas.Function.properties.upgradeInfo (Total Keys: 2)
- schemas.RedirectFunctionUpgradeTrafficRequest (Total Keys: 2)
- schemas.RollbackFunctionUpgradeTrafficRequest (Total Keys: 2)
- schemas.SetupFunctionUpgradeConfigRequest (Total Keys: 2)
- schemas.UpgradeInfo (Total Keys: 6)

#### cloudfunctions:v2alpha

The following keys were added:
- resources.projects.resources.locations.resources.functions.methods.abortFunctionUpgrade (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.commitFunctionUpgrade (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.redirectFunctionUpgradeTraffic (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.rollbackFunctionUpgradeTraffic (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.setupFunctionUpgradeConfig (Total Keys: 12)
- schemas.AbortFunctionUpgradeRequest (Total Keys: 2)
- schemas.CommitFunctionUpgradeRequest (Total Keys: 2)
- schemas.Function.properties.createTime (Total Keys: 3)
- schemas.Function.properties.upgradeInfo (Total Keys: 2)
- schemas.RedirectFunctionUpgradeTrafficRequest (Total Keys: 2)
- schemas.RollbackFunctionUpgradeTrafficRequest (Total Keys: 2)
- schemas.SetupFunctionUpgradeConfigRequest (Total Keys: 2)
- schemas.UpgradeInfo (Total Keys: 6)

#### cloudfunctions:v2beta

The following keys were added:
- resources.projects.resources.locations.resources.functions.methods.abortFunctionUpgrade (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.commitFunctionUpgrade (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.redirectFunctionUpgradeTraffic (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.rollbackFunctionUpgradeTraffic (Total Keys: 12)
- resources.projects.resources.locations.resources.functions.methods.setupFunctionUpgradeConfig (Total Keys: 12)
- schemas.AbortFunctionUpgradeRequest (Total Keys: 2)
- schemas.CommitFunctionUpgradeRequest (Total Keys: 2)
- schemas.Function.properties.createTime (Total Keys: 3)
- schemas.Function.properties.upgradeInfo (Total Keys: 2)
- schemas.RedirectFunctionUpgradeTrafficRequest (Total Keys: 2)
- schemas.RollbackFunctionUpgradeTrafficRequest (Total Keys: 2)
- schemas.SetupFunctionUpgradeConfigRequest (Total Keys: 2)
- schemas.UpgradeInfo (Total Keys: 6)

Author: yoshi-automation

docs/dyn/cloudfunctions_v1.projects.locations.functions.html

@@ -165,9 +165,10 @@ <h3>Method Details</h3>
   },
   &quot;buildId&quot;: &quot;A String&quot;, # Output only. The Cloud Build ID of the latest successful deployment of the function.
   &quot;buildName&quot;: &quot;A String&quot;, # Output only. The Cloud Build Name of the function deployment. `projects//locations//builds/`.
+  &quot;buildServiceAccount&quot;: &quot;A String&quot;, # Optional. A service account the user provides for use with Cloud Build.
   &quot;buildWorkerPool&quot;: &quot;A String&quot;, # Name of the Cloud Build Custom Worker Pool that should be used to build the function. The format of this field is `projects/{project}/locations/{region}/workerPools/{workerPool}` where `{project}` and `{region}` are the project id and region respectively where the worker pool is defined and `{workerPool}` is the short name of the worker pool. If the project id is not the same as the function, then the Cloud Functions Service Agent (`[email protected]`) must be granted the role Cloud Build Custom Workers Builder (`roles/cloudbuild.customworkers.builder`) in the project.
   &quot;description&quot;: &quot;A String&quot;, # User-provided description of a function.
-  &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If `docker_repository` field is specified, this field will be automatically set as `ARTIFACT_REGISTRY`. If unspecified, it currently defaults to `CONTAINER_REGISTRY`. This field may be overridden by the backend for eligible deployments.
+  &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If unspecified, it defaults to `ARTIFACT_REGISTRY`. If `docker_repository` field is specified, this field should either be left unspecified or set to `ARTIFACT_REGISTRY`.
   &quot;dockerRepository&quot;: &quot;A String&quot;, # User managed repository created in Artifact Registry optionally with a customer managed encryption key. If specified, deployments will use Artifact Registry. If unspecified and the deployment is eligible to use Artifact Registry, GCF will create and use a repository named &#x27;gcf-artifacts&#x27; for every deployed region. This is the repository to which the function docker image will be pushed after it is built by Cloud Build. It must match the pattern `projects/{project}/locations/{location}/repositories/{repository}`. Cross-project repositories are not supported. Cross-location repositories are not supported. Repository format must be &#x27;DOCKER&#x27;.
   &quot;entryPoint&quot;: &quot;A String&quot;, # The name of the function (as defined in source code) that will be executed. Defaults to the resource name suffix (ID of the function), if not specified.
   &quot;environmentVariables&quot;: { # Environment variables that shall be available during function execution.
@@ -376,9 +377,10 @@ <h3>Method Details</h3>
   },
   &quot;buildId&quot;: &quot;A String&quot;, # Output only. The Cloud Build ID of the latest successful deployment of the function.
   &quot;buildName&quot;: &quot;A String&quot;, # Output only. The Cloud Build Name of the function deployment. `projects//locations//builds/`.
+  &quot;buildServiceAccount&quot;: &quot;A String&quot;, # Optional. A service account the user provides for use with Cloud Build.
   &quot;buildWorkerPool&quot;: &quot;A String&quot;, # Name of the Cloud Build Custom Worker Pool that should be used to build the function. The format of this field is `projects/{project}/locations/{region}/workerPools/{workerPool}` where `{project}` and `{region}` are the project id and region respectively where the worker pool is defined and `{workerPool}` is the short name of the worker pool. If the project id is not the same as the function, then the Cloud Functions Service Agent (`[email protected]`) must be granted the role Cloud Build Custom Workers Builder (`roles/cloudbuild.customworkers.builder`) in the project.
   &quot;description&quot;: &quot;A String&quot;, # User-provided description of a function.
-  &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If `docker_repository` field is specified, this field will be automatically set as `ARTIFACT_REGISTRY`. If unspecified, it currently defaults to `CONTAINER_REGISTRY`. This field may be overridden by the backend for eligible deployments.
+  &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If unspecified, it defaults to `ARTIFACT_REGISTRY`. If `docker_repository` field is specified, this field should either be left unspecified or set to `ARTIFACT_REGISTRY`.
   &quot;dockerRepository&quot;: &quot;A String&quot;, # User managed repository created in Artifact Registry optionally with a customer managed encryption key. If specified, deployments will use Artifact Registry. If unspecified and the deployment is eligible to use Artifact Registry, GCF will create and use a repository named &#x27;gcf-artifacts&#x27; for every deployed region. This is the repository to which the function docker image will be pushed after it is built by Cloud Build. It must match the pattern `projects/{project}/locations/{location}/repositories/{repository}`. Cross-project repositories are not supported. Cross-location repositories are not supported. Repository format must be &#x27;DOCKER&#x27;.
   &quot;entryPoint&quot;: &quot;A String&quot;, # The name of the function (as defined in source code) that will be executed. Defaults to the resource name suffix (ID of the function), if not specified.
   &quot;environmentVariables&quot;: { # Environment variables that shall be available during function execution.
@@ -523,9 +525,10 @@ <h3>Method Details</h3>
       },
       &quot;buildId&quot;: &quot;A String&quot;, # Output only. The Cloud Build ID of the latest successful deployment of the function.
       &quot;buildName&quot;: &quot;A String&quot;, # Output only. The Cloud Build Name of the function deployment. `projects//locations//builds/`.
+      &quot;buildServiceAccount&quot;: &quot;A String&quot;, # Optional. A service account the user provides for use with Cloud Build.
       &quot;buildWorkerPool&quot;: &quot;A String&quot;, # Name of the Cloud Build Custom Worker Pool that should be used to build the function. The format of this field is `projects/{project}/locations/{region}/workerPools/{workerPool}` where `{project}` and `{region}` are the project id and region respectively where the worker pool is defined and `{workerPool}` is the short name of the worker pool. If the project id is not the same as the function, then the Cloud Functions Service Agent (`[email protected]`) must be granted the role Cloud Build Custom Workers Builder (`roles/cloudbuild.customworkers.builder`) in the project.
       &quot;description&quot;: &quot;A String&quot;, # User-provided description of a function.
-      &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If `docker_repository` field is specified, this field will be automatically set as `ARTIFACT_REGISTRY`. If unspecified, it currently defaults to `CONTAINER_REGISTRY`. This field may be overridden by the backend for eligible deployments.
+      &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If unspecified, it defaults to `ARTIFACT_REGISTRY`. If `docker_repository` field is specified, this field should either be left unspecified or set to `ARTIFACT_REGISTRY`.
       &quot;dockerRepository&quot;: &quot;A String&quot;, # User managed repository created in Artifact Registry optionally with a customer managed encryption key. If specified, deployments will use Artifact Registry. If unspecified and the deployment is eligible to use Artifact Registry, GCF will create and use a repository named &#x27;gcf-artifacts&#x27; for every deployed region. This is the repository to which the function docker image will be pushed after it is built by Cloud Build. It must match the pattern `projects/{project}/locations/{location}/repositories/{repository}`. Cross-project repositories are not supported. Cross-location repositories are not supported. Repository format must be &#x27;DOCKER&#x27;.
       &quot;entryPoint&quot;: &quot;A String&quot;, # The name of the function (as defined in source code) that will be executed. Defaults to the resource name suffix (ID of the function), if not specified.
       &quot;environmentVariables&quot;: { # Environment variables that shall be available during function execution.
@@ -633,9 +636,10 @@ <h3>Method Details</h3>
   },
   &quot;buildId&quot;: &quot;A String&quot;, # Output only. The Cloud Build ID of the latest successful deployment of the function.
   &quot;buildName&quot;: &quot;A String&quot;, # Output only. The Cloud Build Name of the function deployment. `projects//locations//builds/`.
+  &quot;buildServiceAccount&quot;: &quot;A String&quot;, # Optional. A service account the user provides for use with Cloud Build.
   &quot;buildWorkerPool&quot;: &quot;A String&quot;, # Name of the Cloud Build Custom Worker Pool that should be used to build the function. The format of this field is `projects/{project}/locations/{region}/workerPools/{workerPool}` where `{project}` and `{region}` are the project id and region respectively where the worker pool is defined and `{workerPool}` is the short name of the worker pool. If the project id is not the same as the function, then the Cloud Functions Service Agent (`[email protected]`) must be granted the role Cloud Build Custom Workers Builder (`roles/cloudbuild.customworkers.builder`) in the project.
   &quot;description&quot;: &quot;A String&quot;, # User-provided description of a function.
-  &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If `docker_repository` field is specified, this field will be automatically set as `ARTIFACT_REGISTRY`. If unspecified, it currently defaults to `CONTAINER_REGISTRY`. This field may be overridden by the backend for eligible deployments.
+  &quot;dockerRegistry&quot;: &quot;A String&quot;, # Docker Registry to use for this deployment. If unspecified, it defaults to `ARTIFACT_REGISTRY`. If `docker_repository` field is specified, this field should either be left unspecified or set to `ARTIFACT_REGISTRY`.
   &quot;dockerRepository&quot;: &quot;A String&quot;, # User managed repository created in Artifact Registry optionally with a customer managed encryption key. If specified, deployments will use Artifact Registry. If unspecified and the deployment is eligible to use Artifact Registry, GCF will create and use a repository named &#x27;gcf-artifacts&#x27; for every deployed region. This is the repository to which the function docker image will be pushed after it is built by Cloud Build. It must match the pattern `projects/{project}/locations/{location}/repositories/{repository}`. Cross-project repositories are not supported. Cross-location repositories are not supported. Repository format must be &#x27;DOCKER&#x27;.
   &quot;entryPoint&quot;: &quot;A String&quot;, # The name of the function (as defined in source code) that will be executed. Defaults to the resource name suffix (ID of the function), if not specified.
   &quot;environmentVariables&quot;: { # Environment variables that shall be available during function execution.