feat(compute): update the api

#### compute:alpha

The following keys were deleted:
- schemas.FutureReservation.properties.enableOpportunisticMaintenance.type (Total Keys: 1)
- schemas.FutureReservation.properties.instanceTerminationAction.type (Total Keys: 1)
- schemas.GroupMaintenanceInfo.properties.enableOpportunisticMaintenance.type (Total Keys: 1)
- schemas.MultiMig.properties.locationPolicy.$ref (Total Keys: 1)
- schemas.MultiMig.properties.parts (Total Keys: 2)
- schemas.MultiMig.properties.schedulingPolicy.$ref (Total Keys: 1)
- schemas.MultiMigLocationPolicy (Total Keys: 4)
- schemas.MultiMigPart (Total Keys: 4)
- schemas.MultiMigSchedulingPolicy (Total Keys: 3)
- schemas.Reservation.properties.instanceTerminationAction.type (Total Keys: 1)

The following keys were added:
- resources.backendServices.methods.getEffectiveSecurityPolicies (Total Keys: 15)
- resources.crossSiteNetworks.methods.patch.parameters.updateMask (Total Keys: 3)
- resources.licenses.methods.update (Total Keys: 21)
- resources.regionSecurityPolicies.methods.setLabels (Total Keys: 22)
- resources.reservationBlocks.methods.performMaintenance (Total Keys: 24)
- resources.reservations.methods.performMaintenance (Total Keys: 20)
- schemas.BackendServicesGetEffectiveSecurityPoliciesResponse (Total Keys: 4)
- schemas.FutureReservation.properties.aggregateReservation.$ref (Total Keys: 1)
- schemas.FutureReservation.properties.reservationMode.type (Total Keys: 1)
- schemas.InstancesGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.Interconnect.properties.wireGroups (Total Keys: 2)
- schemas.InterconnectLocation.properties.crossSiteInterconnectInfos (Total Keys: 2)
- schemas.InterconnectLocationCrossSiteInterconnectInfo (Total Keys: 5)
- schemas.NetworkProfile.properties.location.$ref (Total Keys: 1)
- schemas.NetworkProfileLocation (Total Keys: 4)
- schemas.NetworkRoutingConfig.properties.effectiveBgpAlwaysCompareMed.type (Total Keys: 1)
- schemas.NetworkRoutingConfig.properties.effectiveBgpInterRegionCost.type (Total Keys: 1)
- schemas.NetworksGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.NodeType.properties.maxVms (Total Keys: 2)
- schemas.RegionNetworkFirewallPoliciesGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.ReservationsBlocksPerformMaintenanceRequest (Total Keys: 3)
- schemas.ReservationsPerformMaintenanceRequest (Total Keys: 3)
- schemas.SecurityPolicyAdvancedOptionsConfig.properties.requestBodyInspectionSize.type (Total Keys: 1)
- schemas.WireGroup.properties.topology.$ref (Total Keys: 1)
- schemas.WireGroupTopology (Total Keys: 8)

#### compute:beta

The following keys were deleted:
- schemas.FutureReservation.properties.enableOpportunisticMaintenance.type (Total Keys: 1)
- schemas.FutureReservation.properties.instanceTerminationAction.type (Total Keys: 1)
- schemas.GroupMaintenanceInfo.properties.enableOpportunisticMaintenance.type (Total Keys: 1)
- schemas.Reservation.properties.instanceTerminationAction.type (Total Keys: 1)

The following keys were added:
- resources.backendServices.methods.getEffectiveSecurityPolicies (Total Keys: 15)
- resources.instances.methods.delete.parameters.noGracefulShutdown (Total Keys: 2)
- resources.instances.methods.stop.parameters.noGracefulShutdown (Total Keys: 2)
- resources.regionSecurityPolicies.methods.setLabels (Total Keys: 22)
- schemas.BackendServicesGetEffectiveSecurityPoliciesResponse (Total Keys: 4)
- schemas.InstancesGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.NetworkProfile.properties.location.$ref (Total Keys: 1)
- schemas.NetworkProfileLocation (Total Keys: 4)
- schemas.NetworkRoutingConfig.properties.effectiveBgpAlwaysCompareMed.type (Total Keys: 1)
- schemas.NetworkRoutingConfig.properties.effectiveBgpInterRegionCost.type (Total Keys: 1)
- schemas.NetworksGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.RegionNetworkFirewallPoliciesGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.ResourceStatus.properties.physicalHostTopology.$ref (Total Keys: 1)
- schemas.ResourceStatus.properties.shutdownDetails.$ref (Total Keys: 1)
- schemas.ResourceStatusPhysicalHostTopology (Total Keys: 6)
- schemas.ResourceStatusShutdownDetails (Total Keys: 6)
- schemas.RouterNat.properties.nat64Subnetworks (Total Keys: 2)
- schemas.RouterNat.properties.sourceSubnetworkIpRangesToNat64.type (Total Keys: 1)
- schemas.RouterNatSubnetworkToNat64 (Total Keys: 3)
- schemas.Scheduling.properties.gracefulShutdown.$ref (Total Keys: 1)
- schemas.SchedulingGracefulShutdown (Total Keys: 4)
- schemas.SecurityPolicyAdvancedOptionsConfig.properties.requestBodyInspectionSize.type (Total Keys: 1)
- schemas.Subnetwork.properties.ipCollection.type (Total Keys: 1)
- schemas.Subnetwork.properties.ipv6GceEndpoint.type (Total Keys: 1)

#### compute:v1

The following keys were added:
- resources.instanceGroupManagers.methods.resumeInstances (Total Keys: 20)
- resources.instanceGroupManagers.methods.startInstances (Total Keys: 20)
- resources.instanceGroupManagers.methods.stopInstances (Total Keys: 20)
- resources.instanceGroupManagers.methods.suspendInstances (Total Keys: 20)
- resources.networkProfiles.methods.get (Total Keys: 15)
- resources.networkProfiles.methods.list (Total Keys: 24)
- resources.regionInstanceGroupManagers.methods.resumeInstances (Total Keys: 20)
- resources.regionInstanceGroupManagers.methods.startInstances (Total Keys: 20)
- resources.regionInstanceGroupManagers.methods.stopInstances (Total Keys: 20)
- resources.regionInstanceGroupManagers.methods.suspendInstances (Total Keys: 20)
- resources.regionSecurityPolicies.methods.setLabels (Total Keys: 22)
- schemas.InstanceGroupManager.properties.standbyPolicy.$ref (Total Keys: 1)
- schemas.InstanceGroupManager.properties.targetStoppedSize (Total Keys: 2)
- schemas.InstanceGroupManager.properties.targetSuspendedSize (Total Keys: 2)
- schemas.InstanceGroupManagerStandbyPolicy (Total Keys: 5)
- schemas.InstanceGroupManagersResumeInstancesRequest (Total Keys: 4)
- schemas.InstanceGroupManagersStartInstancesRequest (Total Keys: 4)
- schemas.InstanceGroupManagersStopInstancesRequest (Total Keys: 5)
- schemas.InstanceGroupManagersSuspendInstancesRequest (Total Keys: 5)
- schemas.Network.properties.networkProfile.type (Total Keys: 1)
- schemas.NetworkProfile (Total Keys: 64)
- schemas.NetworkRoutingConfig.properties.bgpAlwaysCompareMed.type (Total Keys: 1)
- schemas.NetworkRoutingConfig.properties.bgpBestPathSelectionMode.type (Total Keys: 1)
- schemas.NetworkRoutingConfig.properties.bgpInterRegionCost.type (Total Keys: 1)
- schemas.RegionInstanceGroupManagersResumeInstancesRequest (Total Keys: 4)
- schemas.RegionInstanceGroupManagersStartInstancesRequest (Total Keys: 4)
- schemas.RegionInstanceGroupManagersStopInstancesRequest (Total Keys: 5)
- schemas.RegionInstanceGroupManagersSuspendInstancesRequest (Total Keys: 5)
- schemas.Route.properties.nextHopInterRegionCost (Total Keys: 2)
- schemas.Route.properties.nextHopMed (Total Keys: 2)
- schemas.Route.properties.nextHopOrigin.type (Total Keys: 1)

docs/dyn/compute_alpha.crossSiteNetworks.html

@@ -93,7 +93,7 @@ <h2>Instance Methods</h2>
   <code><a href="#list_next">list_next()</a></code></p>
 <p class="firstline">Retrieves the next page of results.</p>
 <p class="toc_element">
-  <code><a href="#patch">patch(project, crossSiteNetwork, body=None, requestId=None, validateOnly=None, x__xgafv=None)</a></code></p>
+  <code><a href="#patch">patch(project, crossSiteNetwork, body=None, requestId=None, updateMask=None, validateOnly=None, x__xgafv=None)</a></code></p>
 <p class="firstline">Updates the specified cross-site network with the data included in the request. This method supports PATCH semantics and uses the JSON merge patch format and processing rules.</p>
 <h3>Method Details</h3>
 <div class="method">
@@ -272,7 +272,7 @@ <h3>Method Details</h3>
 }
 
   requestId: string, An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. 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). end_interface: MixerMutationRequestBuilder
-  validateOnly: boolean, [Input Only] Validate the new configuration, but don&#x27;t create it. If applicable, any configuration notices are returned in the `configurationNotices` field.
+  validateOnly: boolean, [Input Only] Validate the new configuration, but don&#x27;t create it.
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format
@@ -457,7 +457,7 @@ <h3>Method Details</h3>
 </div>
 
 <div class="method">
-    <code class="details" id="patch">patch(project, crossSiteNetwork, body=None, requestId=None, validateOnly=None, x__xgafv=None)</code>
+    <code class="details" id="patch">patch(project, crossSiteNetwork, body=None, requestId=None, updateMask=None, validateOnly=None, x__xgafv=None)</code>
   <pre>Updates the specified cross-site network with the data included in the request. This method supports PATCH semantics and uses the JSON merge patch format and processing rules.
 
 Args:
@@ -477,7 +477,8 @@ <h3>Method Details</h3>
 }
 
   requestId: string, An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. 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). end_interface: MixerMutationRequestBuilder
-  validateOnly: boolean, [Input Only] Validate the new configuration, but don&#x27;t update it. If applicable, any configuration notices are returned in the `configurationNotices` field.
+  updateMask: string, update_mask indicates fields to be updated as part of this request.
+  validateOnly: boolean, [Input Only] Validate the new configuration, but don&#x27;t update it.
   x__xgafv: string, V1 error format.
     Allowed values
       1 - v1 error format

docs/dyn/compute_alpha.disks.html

@@ -1106,7 +1106,7 @@ <h3>Method Details</h3>
     {
   &quot;asyncReplicationStatus&quot;: {
     &quot;diskPairReplicationState&quot;: {
-      &quot;dataReplicationState&quot;: &quot;A String&quot;, # [Output Only] The status of disk creation. - ASYNC_REPLICATION_STATE_INITIALIZING: The device is doing the initial replication after starting the replication. - ASYNC_REPLICATION_STATE_REPLICATING_HEALTHY: The primary disk is healthily replicating to the secondary device i.e. last_replication_time is within RPO. - ASYNC_REPLICATION_STATE_REPLICATING_BEHIND: The replication is lagging above the SLO limit due to some internal issue. - ASYNC_REPLICATION_STATE_REPLICATING_UNHEALTHY: The replication is lagging, and the RPO is not being met due to some internal issue. . - ASYNC_REPLICATION_STATE_REPLICATION_STUCK: The replication is completely stuck due to some internal error. - ASYNC_REPLICATION_STATE_STOPPING: The replication is under the process of being stopped. This is a transient state. - ASYNC_REPLICATION_STATE_STOPPED: The replication between the disk-pairs have stopped.
+      &quot;dataReplicationState&quot;: &quot;A String&quot;, # [Output Only] The status of disk creation. - ASYNC_REPLICATION_STATE_INITIALIZING: The device is doing the initial replication after starting the replication. - ASYNC_REPLICATION_STATE_REPLICATING_HEALTHY: The primary disk is healthily replicating to the secondary device i.e. last_replication_time is within RPO. - ASYNC_REPLICATION_STATE_REPLICATING_BEHIND_HIGH_CHURN: The replication is lagging above the SLO limit due to some internal issue. - ASYNC_REPLICATION_STATE_REPLICATING_BEHIND_SYSTEM_LAGGING: The replication is lagging, and the RPO is not being met due to some internal issue. - ASYNC_REPLICATION_STATE_REPLICATION_STUCK: The replication is completely stuck due to some internal error. - ASYNC_REPLICATION_STATE_STOPPING: The replication is under the process of being stopped. This is a transient state. - ASYNC_REPLICATION_STATE_STOPPED: The replication between the disk-pairs have stopped.
       &quot;replicationDiskPair&quot;: {
         &quot;primaryDisk&quot;: &quot;A String&quot;, # URL of the primary disk.
         &quot;secondaryDisk&quot;: &quot;A String&quot;, # URL of the secondary disk.