feat(compute): update the api

#### compute:alpha

The following keys were deleted:
- schemas.NetworkProfile.properties.zone.type (Total Keys: 1)

The following keys were added:
- resources.interconnectGroups.methods.createMembers (Total Keys: 16)
- schemas.BackendService.properties.dynamicForwarding.$ref (Total Keys: 1)
- schemas.BackendServiceDynamicForwarding (Total Keys: 6)
- schemas.InterconnectAttachmentGroupsOperationalStatus.properties.attachmentStatuses (Total Keys: 2)
- schemas.InterconnectAttachmentGroupsOperationalStatus.properties.configured.$ref (Total Keys: 1)
- schemas.InterconnectAttachmentGroupsOperationalStatus.properties.intent.$ref (Total Keys: 1)
- schemas.InterconnectAttachmentGroupsOperationalStatus.properties.operational.$ref (Total Keys: 1)
- schemas.InterconnectAttachmentGroupsOperationalStatusAttachmentStatus (Total Keys: 6)
- schemas.InterconnectGroupsCreateMembers (Total Keys: 28)
- schemas.MachineImage.properties.params.$ref (Total Keys: 1)
- schemas.MachineImageParams (Total Keys: 6)
- schemas.ResourcePolicySnapshotSchedulePolicySnapshotProperties.properties.region.type (Total Keys: 1)
- schemas.ResourcePolicyWorkloadPolicy.properties.acceleratorTopology.type (Total Keys: 1)
- schemas.ResourcePolicyWorkloadPolicy.properties.maxTopologyDistance.type (Total Keys: 1)
- schemas.SnapshotSettingsAccessLocation.properties.policy.type (Total Keys: 1)
- schemas.VpnTunnel.properties.cipherSuite.$ref (Total Keys: 1)
- schemas.VpnTunnelCipherSuite (Total Keys: 4)
- schemas.VpnTunnelPhase1Algorithms (Total Keys: 10)
- schemas.VpnTunnelPhase2Algorithms (Total Keys: 8)

#### compute:beta

The following keys were deleted:
- schemas.NetworkProfile.properties.zone.type (Total Keys: 1)

The following keys were added:
- resources.advice.methods.calendarMode (Total Keys: 16)
- resources.reservationBlocks.methods.performMaintenance (Total Keys: 24)
- resources.reservations.methods.performMaintenance (Total Keys: 20)
- schemas.CalendarModeAdviceRequest (Total Keys: 4)
- schemas.CalendarModeAdviceResponse (Total Keys: 4)
- schemas.CalendarModeRecommendation (Total Keys: 4)
- schemas.FlexibleTimeRange (Total Keys: 14)
- schemas.FutureResourcesRecommendation (Total Keys: 15)
- schemas.FutureResourcesSpec (Total Keys: 35)
- schemas.InstanceGroupManagerInstanceLifecyclePolicy.properties.onFailedHealthCheck.type (Total Keys: 1)
- schemas.Interconnect.properties.wireGroups (Total Keys: 2)
- schemas.NodeType.properties.maxVms (Total Keys: 2)
- schemas.ReservationsBlocksPerformMaintenanceRequest (Total Keys: 3)
- schemas.ReservationsPerformMaintenanceRequest (Total Keys: 3)

#### compute:v1

The following keys were deleted:
- schemas.NetworkProfile.properties.zone.type (Total Keys: 1)

The following keys were added:
- resources.networkFirewallPolicies.methods.addPacketMirroringRule (Total Keys: 24)
- resources.networkFirewallPolicies.methods.getPacketMirroringRule (Total Keys: 18)
- resources.networkFirewallPolicies.methods.patchPacketMirroringRule (Total Keys: 21)
- resources.networkFirewallPolicies.methods.removePacketMirroringRule (Total Keys: 20)
- schemas.FirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.InstancesGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.NetworksGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)
- schemas.NodeType.properties.maxVms (Total Keys: 2)
- schemas.RegionNetworkFirewallPoliciesGetEffectiveFirewallsResponseEffectiveFirewallPolicy.properties.packetMirroringRules (Total Keys: 2)

Author: yoshi-automation

docs/dyn/compute_alpha.backendServices.html

@@ -411,6 +411,11 @@ <h3>Method Details</h3>
             &quot;A String&quot;,
           ],
           &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+          &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+            &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+              &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+            },
+          },
           &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
           &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
           &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.
@@ -1203,6 +1208,11 @@ <h3>Method Details</h3>
     &quot;A String&quot;,
   ],
   &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+  &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+    &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+      &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+    },
+  },
   &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
   &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
   &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.
@@ -2073,6 +2083,11 @@ <h3>Method Details</h3>
     &quot;A String&quot;,
   ],
   &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+  &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+    &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+      &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+    },
+  },
   &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
   &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
   &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.
@@ -2689,6 +2704,11 @@ <h3>Method Details</h3>
         &quot;A String&quot;,
       ],
       &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+      &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+        &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+          &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+        },
+      },
       &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
       &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
       &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.
@@ -3203,6 +3223,11 @@ <h3>Method Details</h3>
         &quot;A String&quot;,
       ],
       &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+      &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+        &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+          &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+        },
+      },
       &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
       &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
       &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.
@@ -3733,6 +3758,11 @@ <h3>Method Details</h3>
     &quot;A String&quot;,
   ],
   &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+  &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+    &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+      &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+    },
+  },
   &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
   &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
   &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.
@@ -4732,6 +4762,11 @@ <h3>Method Details</h3>
     &quot;A String&quot;,
   ],
   &quot;description&quot;: &quot;A String&quot;, # An optional description of this resource. Provide this property when you create the resource.
+  &quot;dynamicForwarding&quot;: { # Defines a dynamic forwarding configuration for the backend service. # Dynamic forwarding configuration. This field is used to configure the backend service with dynamic forwarding feature which together with Service Extension allows customized and complex routing logic.
+    &quot;ipPortSelection&quot;: { # Defines a IP:PORT based dynamic forwarding configuration for the backend service. Some ranges are restricted: Restricted ranges. # IP:PORT based dynamic forwarding configuration.
+      &quot;enabled&quot;: True or False, # A boolean flag enabling IP:PORT based dynamic forwarding.
+    },
+  },
   &quot;edgeSecurityPolicy&quot;: &quot;A String&quot;, # [Output Only] The resource URL for the edge security policy associated with this backend service.
   &quot;enableCDN&quot;: True or False, # If true, enables Cloud CDN for the backend service of a global external Application Load Balancer.
   &quot;externalManagedMigrationState&quot;: &quot;A String&quot;, # Specifies the canary migration state. Possible values are PREPARE, TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state must be changed to PREPARE. The state must be changed to TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate traffic by percentage using externalManagedMigrationTestingPercentage. Rolling back a migration requires the states to be set in reverse order. So changing the scheme from EXTERNAL_MANAGED to EXTERNAL requires the state to be set to TEST_ALL_TRAFFIC at the same time. Optionally, the TEST_BY_PERCENTAGE state can be used to migrate some traffic back to EXTERNAL or PREPARE can be used to migrate all traffic back to EXTERNAL.