feat(clouddeploy): update the api

#### clouddeploy:v1

The following keys were added:
- schemas.CustomTargetTypeNotificationEvent (Total Keys: 6)
- schemas.DeployPolicyNotificationEvent (Total Keys: 6)
- schemas.GatewayServiceMesh.properties.podSelectorLabel.type (Total Keys: 1)
- schemas.ServiceNetworking.properties.podSelectorLabel.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/clouddeploy_v1.projects.locations.customTargetTypes.html

@@ -112,7 +112,7 @@ <h3>Method Details</h3>
   <pre>Creates a new CustomTargetType in a given project and location.
 
 Args:
-  parent: string, Required. The parent collection in which the `CustomTargetType` should be created. Format should be `projects/{project_id}/locations/{location_name}`. (required)
+  parent: string, Required. The parent collection in which the `CustomTargetType` must be created. The format is `projects/{project_id}/locations/{location_name}`. (required)
   body: object, The request body.
     The object takes the form of:
 
@@ -466,7 +466,7 @@ <h3>Method Details</h3>
 
   allowMissing: boolean, Optional. If set to true, updating a `CustomTargetType` that does not exist will result in the creation of a new `CustomTargetType`.
   requestId: string, Optional. A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server knows to ignore the request if it has already been completed. The server guarantees that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
-  updateMask: string, Required. Field mask is used to specify the fields to be overwritten in the `CustomTargetType` resource by the update. The fields specified in the update_mask are relative to the resource, not the full request. A field will be overwritten if it&#x27;s in the mask. If the user doesn&#x27;t provide a mask then all fields are overwritten.
+  updateMask: string, Required. Field mask is used to specify the fields to be overwritten by the update in the `CustomTargetType` resource. The fields specified in the update_mask are relative to the resource, not the full request. A field will be overwritten if it&#x27;s in the mask. If the user doesn&#x27;t provide a mask then all fields are overwritten.
   validateOnly: boolean, Optional. If set to true, the request is validated and the user is provided with an expected result, but no actual change is made.
   x__xgafv: string, V1 error format.
     Allowed values

docs/dyn/clouddeploy_v1.projects.locations.deliveryPipelines.automationRuns.html

@@ -170,7 +170,7 @@ <h3>Method Details</h3>
           ],
           &quot;wait&quot;: &quot;A String&quot;, # Optional. How long to wait after a rollout is finished.
         },
-        &quot;promoteReleaseRule&quot;: { # `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
+        &quot;promoteReleaseRule&quot;: { # The `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
           &quot;condition&quot;: { # `AutomationRuleCondition` contains conditions relevant to an `Automation` rule. # Output only. Information around the state of the Automation rule.
             &quot;targetsPresentCondition&quot;: { # `TargetsPresentCondition` contains information on any Targets referenced in the Delivery Pipeline that do not actually exist. # Optional. Details around targets enumerated in the rule.
               &quot;missingTargets&quot;: [ # The list of Target names that do not exist. For example, `projects/{project_id}/locations/{location_name}/targets/{target_name}`.
@@ -321,7 +321,7 @@ <h3>Method Details</h3>
               ],
               &quot;wait&quot;: &quot;A String&quot;, # Optional. How long to wait after a rollout is finished.
             },
-            &quot;promoteReleaseRule&quot;: { # `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
+            &quot;promoteReleaseRule&quot;: { # The `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
               &quot;condition&quot;: { # `AutomationRuleCondition` contains conditions relevant to an `Automation` rule. # Output only. Information around the state of the Automation rule.
                 &quot;targetsPresentCondition&quot;: { # `TargetsPresentCondition` contains information on any Targets referenced in the Delivery Pipeline that do not actually exist. # Optional. Details around targets enumerated in the rule.
                   &quot;missingTargets&quot;: [ # The list of Target names that do not exist. For example, `projects/{project_id}/locations/{location_name}/targets/{target_name}`.

docs/dyn/clouddeploy_v1.projects.locations.deliveryPipelines.automations.html

@@ -106,7 +106,7 @@ <h3>Method Details</h3>
   <pre>Creates a new Automation in a given project and location.
 
 Args:
-  parent: string, Required. The parent collection in which the `Automation` should be created. Format should be `projects/{project_id}/locations/{location_name}/deliveryPipelines/{pipeline_name}`. (required)
+  parent: string, Required. The parent collection in which the `Automation` must be created. The format is `projects/{project_id}/locations/{location_name}/deliveryPipelines/{pipeline_name}`. (required)
   body: object, The request body.
     The object takes the form of:
 
@@ -139,7 +139,7 @@ <h3>Method Details</h3>
         ],
         &quot;wait&quot;: &quot;A String&quot;, # Optional. How long to wait after a rollout is finished.
       },
-      &quot;promoteReleaseRule&quot;: { # `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
+      &quot;promoteReleaseRule&quot;: { # The `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
         &quot;condition&quot;: { # `AutomationRuleCondition` contains conditions relevant to an `Automation` rule. # Output only. Information around the state of the Automation rule.
           &quot;targetsPresentCondition&quot;: { # `TargetsPresentCondition` contains information on any Targets referenced in the Delivery Pipeline that do not actually exist. # Optional. Details around targets enumerated in the rule.
             &quot;missingTargets&quot;: [ # The list of Target names that do not exist. For example, `projects/{project_id}/locations/{location_name}/targets/{target_name}`.
@@ -224,7 +224,7 @@ <h3>Method Details</h3>
   <pre>Deletes a single Automation resource.
 
 Args:
-  name: string, Required. The name of the `Automation` to delete. Format should be `projects/{project_id}/locations/{location_name}/deliveryPipelines/{pipeline_name}/automations/{automation_name}`. (required)
+  name: string, Required. The name of the `Automation` to delete. The format is `projects/{project_id}/locations/{location_name}/deliveryPipelines/{pipeline_name}/automations/{automation_name}`. (required)
   allowMissing: boolean, Optional. If set to true, then deleting an already deleted or non-existing `Automation` will succeed.
   etag: string, Optional. The weak etag of the request. This checksum is computed by the server based on the value of other fields, and may be sent on update and delete requests to ensure the client has an up-to-date value before proceeding.
   requestId: string, Optional. A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server knows to ignore the request if it has already been completed. The server guarantees that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
@@ -301,7 +301,7 @@ <h3>Method Details</h3>
         ],
         &quot;wait&quot;: &quot;A String&quot;, # Optional. How long to wait after a rollout is finished.
       },
-      &quot;promoteReleaseRule&quot;: { # `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
+      &quot;promoteReleaseRule&quot;: { # The `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
         &quot;condition&quot;: { # `AutomationRuleCondition` contains conditions relevant to an `Automation` rule. # Output only. Information around the state of the Automation rule.
           &quot;targetsPresentCondition&quot;: { # `TargetsPresentCondition` contains information on any Targets referenced in the Delivery Pipeline that do not actually exist. # Optional. Details around targets enumerated in the rule.
             &quot;missingTargets&quot;: [ # The list of Target names that do not exist. For example, `projects/{project_id}/locations/{location_name}/targets/{target_name}`.
@@ -399,7 +399,7 @@ <h3>Method Details</h3>
             ],
             &quot;wait&quot;: &quot;A String&quot;, # Optional. How long to wait after a rollout is finished.
           },
-          &quot;promoteReleaseRule&quot;: { # `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
+          &quot;promoteReleaseRule&quot;: { # The `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
             &quot;condition&quot;: { # `AutomationRuleCondition` contains conditions relevant to an `Automation` rule. # Output only. Information around the state of the Automation rule.
               &quot;targetsPresentCondition&quot;: { # `TargetsPresentCondition` contains information on any Targets referenced in the Delivery Pipeline that do not actually exist. # Optional. Details around targets enumerated in the rule.
                 &quot;missingTargets&quot;: [ # The list of Target names that do not exist. For example, `projects/{project_id}/locations/{location_name}/targets/{target_name}`.
@@ -506,7 +506,7 @@ <h3>Method Details</h3>
         ],
         &quot;wait&quot;: &quot;A String&quot;, # Optional. How long to wait after a rollout is finished.
       },
-      &quot;promoteReleaseRule&quot;: { # `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
+      &quot;promoteReleaseRule&quot;: { # The `PromoteRelease` rule will automatically promote a release from the current target to a specified target. # Optional. `PromoteReleaseRule` will automatically promote a release from the current target to a specified target.
         &quot;condition&quot;: { # `AutomationRuleCondition` contains conditions relevant to an `Automation` rule. # Output only. Information around the state of the Automation rule.
           &quot;targetsPresentCondition&quot;: { # `TargetsPresentCondition` contains information on any Targets referenced in the Delivery Pipeline that do not actually exist. # Optional. Details around targets enumerated in the rule.
             &quot;missingTargets&quot;: [ # The list of Target names that do not exist. For example, `projects/{project_id}/locations/{location_name}/targets/{target_name}`.
@@ -556,7 +556,7 @@ <h3>Method Details</h3>
 
   allowMissing: boolean, Optional. If set to true, updating a `Automation` that does not exist will result in the creation of a new `Automation`.
   requestId: string, Optional. A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server knows to ignore the request if it has already been completed. The server guarantees that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
-  updateMask: string, Required. Field mask is used to specify the fields to be overwritten in the `Automation` resource by the update. The fields specified in the update_mask are relative to the resource, not the full request. A field will be overwritten if it&#x27;s in the mask. If the user doesn&#x27;t provide a mask then all fields are overwritten.
+  updateMask: string, Required. Field mask is used to specify the fields to be overwritten by the update in the `Automation` resource. The fields specified in the update_mask are relative to the resource, not the full request. A field will be overwritten if it&#x27;s in the mask. If the user doesn&#x27;t provide a mask then all fields are overwritten.
   validateOnly: boolean, Optional. If set to true, the request is validated and the user is provided with an expected result, but no actual change is made.
   x__xgafv: string, V1 error format.
     Allowed values