Skip to content

Commit

Permalink
feat(compute): update the API
Browse files Browse the repository at this point in the history 
#### compute:alpha

The following keys were changed:
- resources.instanceGroupManagers.methods.recreateInstances.description
- resources.instances.methods.delete.description
- resources.regionInstanceGroupManagers.methods.recreateInstances.description
- schemas.BackendService.properties.sessionAffinity.description
- schemas.InterconnectAttachment.properties.encryption.description
- schemas.InterconnectAttachment.properties.ipsecInternalAddresses.description
- schemas.RegionInstanceGroupManagersDeleteInstancesRequest.properties.skipInapplicableInstances.description
- schemas.Router.properties.encryptedInterconnectRouter.description
- schemas.SecurityPolicyRule.properties.action.description
- schemas.Subnetwork.properties.metadata.description
- schemas.SubnetworkLogConfig.properties.metadata.description
- schemas.VpnGatewayVpnGatewayInterface.properties.interconnectAttachment.description
- schemas.VpnTunnel.properties.status.description

#### compute:beta

The following keys were added:
- resources.imageFamilyViews.methods.get.description
- resources.imageFamilyViews.methods.get.httpMethod
- resources.imageFamilyViews.methods.get.id
- resources.imageFamilyViews.methods.get.parameterOrder
- resources.imageFamilyViews.methods.get.parameters.family.description
- resources.imageFamilyViews.methods.get.parameters.family.location
- resources.imageFamilyViews.methods.get.parameters.family.pattern
- resources.imageFamilyViews.methods.get.parameters.family.required
- resources.imageFamilyViews.methods.get.parameters.family.type
- resources.imageFamilyViews.methods.get.parameters.project.description
- resources.imageFamilyViews.methods.get.parameters.project.location
- resources.imageFamilyViews.methods.get.parameters.project.pattern
- resources.imageFamilyViews.methods.get.parameters.project.required
- resources.imageFamilyViews.methods.get.parameters.project.type
- resources.imageFamilyViews.methods.get.parameters.zone.description
- resources.imageFamilyViews.methods.get.parameters.zone.location
- resources.imageFamilyViews.methods.get.parameters.zone.pattern
- resources.imageFamilyViews.methods.get.parameters.zone.required
- resources.imageFamilyViews.methods.get.parameters.zone.type
- resources.imageFamilyViews.methods.get.path
- resources.imageFamilyViews.methods.get.response.$ref
- resources.imageFamilyViews.methods.get.scopes
- schemas.HealthStatus.properties.forwardingRule.description
- schemas.HealthStatus.properties.forwardingRule.type
- schemas.HealthStatus.properties.forwardingRuleIp.description
- schemas.HealthStatus.properties.forwardingRuleIp.type
- schemas.ImageFamilyView.id
- schemas.ImageFamilyView.properties.image.$ref
- schemas.ImageFamilyView.properties.image.description
- schemas.ImageFamilyView.type

The following keys were changed:
- resources.instanceGroupManagers.methods.recreateInstances.description
- resources.instances.methods.delete.description
- resources.regionInstanceGroupManagers.methods.recreateInstances.description
- schemas.BackendService.properties.sessionAffinity.description
- schemas.BackendService.properties.sessionAffinity.enum
- schemas.BackendService.properties.sessionAffinity.enumDescriptions
- schemas.InterconnectAttachment.properties.encryption.description
- schemas.InterconnectAttachment.properties.ipsecInternalAddresses.description
- schemas.Router.properties.encryptedInterconnectRouter.description
- schemas.SecurityPolicyRule.properties.action.description
- schemas.SubnetworkLogConfig.properties.metadata.description
- schemas.TargetPool.properties.sessionAffinity.enum
- schemas.TargetPool.properties.sessionAffinity.enumDescriptions
- schemas.VpnGatewayVpnGatewayInterface.properties.interconnectAttachment.description
- schemas.VpnTunnel.properties.status.description

#### compute:v1

The following keys were added:
- schemas.AutoscalingPolicyCpuUtilization.properties.predictiveMethod.description
- schemas.AutoscalingPolicyCpuUtilization.properties.predictiveMethod.enum
- schemas.AutoscalingPolicyCpuUtilization.properties.predictiveMethod.enumDescriptions
- schemas.AutoscalingPolicyCpuUtilization.properties.predictiveMethod.type
- schemas.BackendBucketCdnPolicy.properties.requestCoalescing.description
- schemas.BackendBucketCdnPolicy.properties.requestCoalescing.type
- schemas.BackendServiceCdnPolicy.properties.requestCoalescing.description
- schemas.BackendServiceCdnPolicy.properties.requestCoalescing.type
- schemas.DistributionPolicy.properties.targetShape.description
- schemas.DistributionPolicy.properties.targetShape.enum
- schemas.DistributionPolicy.properties.targetShape.enumDescriptions
- schemas.DistributionPolicy.properties.targetShape.type
- schemas.HealthStatus.properties.forwardingRule.description
- schemas.HealthStatus.properties.forwardingRule.type
- schemas.HealthStatus.properties.forwardingRuleIp.description
- schemas.HealthStatus.properties.forwardingRuleIp.type

The following keys were changed:
- resources.instanceGroupManagers.methods.recreateInstances.description
- resources.instances.methods.delete.description
- resources.regionInstanceGroupManagers.methods.recreateInstances.description
- schemas.BackendService.properties.sessionAffinity.description
- schemas.BackendService.properties.sessionAffinity.enum
- schemas.BackendService.properties.sessionAffinity.enumDescriptions
- schemas.InterconnectAttachment.properties.encryption.description
- schemas.InterconnectAttachment.properties.ipsecInternalAddresses.description
- schemas.Router.properties.encryptedInterconnectRouter.description
- schemas.SecurityPolicyRule.properties.action.description
- schemas.SubnetworkLogConfig.properties.metadata.description
- schemas.TargetPool.properties.sessionAffinity.enum
- schemas.TargetPool.properties.sessionAffinity.enumDescriptions
- schemas.VpnGatewayVpnGatewayInterface.properties.interconnectAttachment.description
- schemas.VpnTunnel.properties.status.description
  • Loading branch information
@yoshi-automation @sofisl
yoshi-automation authored and sofisl committed Apr 5, 2021
1 parent 93d4108 commit 0d7e3fb
Show file tree
Hide file tree
Showing 6 changed files with 393 additions and 64 deletions.
30 changes: 15 additions & 15 deletions discovery/compute-alpha.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
"description": "Creates and runs virtual machines on Google Cloud Platform.",
"discoveryVersion": "v1",
"documentationLink": "https://developers.google.com/compute/docs/reference/latest/",
"etag": "\"uWj2hSb4GVjzdDlAnRd2gbM1ZQ8/q86KO_TM075jWLyNAiNZlSqSxJ8\"",
"etag": "\"uWj2hSb4GVjzdDlAnRd2gbM1ZQ8/hiqisWl0t7KcM6BliB4xmOOmOxg\"",
"icons": {
"x16": "https://www.google.com/images/icons/product/compute_engine-16.png",
"x32": "https://www.google.com/images/icons/product/compute_engine-32.png"
Expand Down Expand Up @@ -8020,7 +8020,7 @@
]
},
"recreateInstances": {
"description": "Flags the specified instances in the managed instance group to be immediately recreated. The instances are deleted and recreated using the current instance template for the managed instance group. This operation is marked as DONE when the flag is set even if the instances have not yet been recreated. You must separately verify the status of the recreating action with the listmanagedinstances method.\n\nIf the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.\n\nYou can specify a maximum of 1000 instances with this method per request.",
"description": "Flags the specified VM instances in the managed instance group to be immediately recreated. Each instance is recreated using the group's current configuration. This operation is marked as DONE when the flag is set even if the instances have not yet been recreated. You must separately verify the status of each instance by checking its currentAction field; for more information, see Checking the status of managed instances.\n\nIf the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.\n\nYou can specify a maximum of 1000 instances with this method per request.",
"httpMethod": "POST",
"id": "compute.instanceGroupManagers.recreateInstances",
"parameterOrder": [
Expand Down Expand Up @@ -9678,7 +9678,7 @@
]
},
"delete": {
"description": "Deletes the specified Instance resource. For more information, see Stopping or Deleting an Instance.",
"description": "Deletes the specified Instance resource. For more information, see Deleting an instance.",
"httpMethod": "DELETE",
"id": "compute.instances.delete",
"parameterOrder": [
Expand Down Expand Up @@ -22141,7 +22141,7 @@
]
},
"recreateInstances": {
"description": "Flags the specified instances in the managed instance group to be immediately recreated. The instances are deleted and recreated using the current instance template for the managed instance group. This operation is marked as DONE when the flag is set even if the instances have not yet been recreated. You must separately verify the status of the recreating action with the listmanagedinstances method.\n\nIf the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.\n\nYou can specify a maximum of 1000 instances with this method per request.",
"description": "Flags the specified VM instances in the managed instance group to be immediately recreated. Each instance is recreated using the group's current configuration. This operation is marked as DONE when the flag is set even if the instances have not yet been recreated. You must separately verify the status of each instance by checking its currentAction field; for more information, see Checking the status of managed instances.\n\nIf the group is part of a backend service that has enabled connection draining, it can take up to 60 seconds after the connection draining duration has elapsed before the VM instance is removed or deleted.\n\nYou can specify a maximum of 1000 instances with this method per request.",
"httpMethod": "POST",
"id": "compute.regionInstanceGroupManagers.recreateInstances",
"parameterOrder": [
Expand Down Expand Up @@ -35557,7 +35557,7 @@
}
}
},
"revision": "20210310",
"revision": "20210316",
"rootUrl": "https://compute.googleapis.com/",
"schemas": {
"AcceleratorConfig": {
Expand Down Expand Up @@ -38336,7 +38336,7 @@
"type": "string"
},
"sessionAffinity": {
"description": "Type of session affinity to use. The default is NONE.\n\nWhen the loadBalancingScheme is EXTERNAL: * For Network Load Balancing, the possible values are NONE, CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO. * For all other load balancers that use loadBalancingScheme=EXTERNAL, the possible values are NONE, CLIENT_IP, or GENERATED_COOKIE. * You can use GENERATED_COOKIE if the protocol is HTTP, HTTP2, or HTTPS.\n\nWhen the loadBalancingScheme is INTERNAL, possible values are NONE, CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO.\n\nWhen the loadBalancingScheme is INTERNAL_SELF_MANAGED, or INTERNAL_MANAGED, possible values are NONE, CLIENT_IP, GENERATED_COOKIE, HEADER_FIELD, or HTTP_COOKIE.\n\nNot supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true.",
"description": "Type of session affinity to use. The default is NONE.\n\nWhen the loadBalancingScheme is EXTERNAL: * For Network Load Balancing, the possible values are NONE, CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO. * For all other load balancers that use loadBalancingScheme=EXTERNAL, the possible values are NONE, CLIENT_IP, or GENERATED_COOKIE. * You can use GENERATED_COOKIE if the protocol is HTTP, HTTP2, or HTTPS.\n\nWhen the loadBalancingScheme is INTERNAL, possible values are NONE, CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO.\n\nWhen the loadBalancingScheme is INTERNAL_SELF_MANAGED, or INTERNAL_MANAGED, possible values are NONE, CLIENT_IP, GENERATED_COOKIE, HEADER_FIELD, or HTTP_COOKIE.\n\nNot supported when the backend service is referenced by a URL map that is bound to target gRPC proxy that has validateForProxyless field set to true.",
"enum": [
"CLIENT_IP",
"CLIENT_IP_NO_DESTINATION",
Expand Down Expand Up @@ -49646,7 +49646,7 @@
"type": "string"
},
"encryption": {
"description": "Indicates the user-supplied encryption option of this interconnect attachment: \n- NONE is the default value, which means that the attachment carries unencrypted traffic. VMs can send traffic to, or receive traffic from, this type of attachment. \n- IPSEC indicates that the attachment carries only traffic encrypted by an IPsec device such as an HA VPN gateway. VMs cannot directly send traffic to, or receive traffic from, such an attachment. To use IPsec-encrypted Cloud Interconnect, create the attachment using this option.",
"description": "Indicates the user-supplied encryption option of this interconnect attachment: \n- NONE is the default value, which means that the attachment carries unencrypted traffic. VMs can send traffic to, or receive traffic from, this type of attachment. \n- IPSEC indicates that the attachment carries only traffic encrypted by an IPsec device such as an HA VPN gateway. VMs cannot directly send traffic to, or receive traffic from, such an attachment. To use IPsec-encrypted Cloud Interconnect, create the attachment using this option. \nNot currently available in all Interconnect locations.",
"enum": [
"IPSEC",
"NONE"
Expand All @@ -49671,7 +49671,7 @@
"type": "string"
},
"ipsecInternalAddresses": {
"description": "URL of addresses that have been reserved for the interconnect attachment, Used only for interconnect attachment that has the encryption option as IPSEC. The addresses must be RFC 1918 IP address ranges. When creating HA VPN gateway over the interconnect attachment, if the attachment is configured to use an RFC 1918 IP address, then the VPN gateway?s IP address will be allocated from the IP address range specified here. For example, if the HA VPN gateway?s interface 0 is paired to this interconnect attachment, then an RFC 1918 IP address for the VPN gateway interface 0 will be allocated from the IP address specified for this interconnect attachment. If this field is not specified for interconnect attachment that has encryption option as IPSEC, later on when creating HA VPN gateway on this interconnect attachment, the HA VPN gateway's IP address will be allocated from regional external IP address pool.",
"description": "URL of addresses that have been reserved for the interconnect attachment, Used only for interconnect attachment that has the encryption option as IPSEC. The addresses must be RFC 1918 IP address ranges. When creating HA VPN gateway over the interconnect attachment, if the attachment is configured to use an RFC 1918 IP address, then the VPN gateway?s IP address will be allocated from the IP address range specified here. For example, if the HA VPN gateway?s interface 0 is paired to this interconnect attachment, then an RFC 1918 IP address for the VPN gateway interface 0 will be allocated from the IP address specified for this interconnect attachment. If this field is not specified for interconnect attachment that has encryption option as IPSEC, later on when creating HA VPN gateway on this interconnect attachment, the HA VPN gateway's IP address will be allocated from regional external IP address pool.\nNot currently available in all Interconnect locations.",
"items": {
"type": "string"
},
Expand Down Expand Up @@ -59505,7 +59505,7 @@
"type": "array"
},
"skipInapplicableInstances": {
"description": "Skip instances which cannot be deleted (instances not belonging to this managed group, already being deleted or being abandoned). If `false`, fail whole flow, if such instance is passed.",
"description": "Skip instances which cannot be deleted (instances not belonging to this managed group, already being deleted or being abandoned). If `false`, fail whole flow, if such instance is passed. DEPRECATED: Use skip_instances_on_validation_error instead.",
"type": "boolean"
}
},
Expand Down Expand Up @@ -61820,7 +61820,7 @@
"type": "string"
},
"encryptedInterconnectRouter": {
"description": "Field to indicate if a router is dedicated to use with encrypted Interconnect Attachment (IPsec-encrypted Cloud Interconnect feature).",
"description": "Field to indicate if a router is dedicated to use with encrypted Interconnect Attachment (IPsec-encrypted Cloud Interconnect feature).\nNot currently available in all Interconnect locations.",
"type": "boolean"
},
"id": {
Expand Down Expand Up @@ -63648,7 +63648,7 @@
"id": "SecurityPolicyRule",
"properties": {
"action": {
"description": "The Action to preform when the client connection triggers the rule. Can currently be either \"allow\" or \"deny()\" where valid values for status are 403, 404, and 502.",
"description": "The Action to perform when the client connection triggers the rule. Can currently be either \"allow\" or \"deny()\" where valid values for status are 403, 404, and 502.",
"type": "string"
},
"description": {
Expand Down Expand Up @@ -66008,7 +66008,7 @@
"description": "This field denotes the VPC flow logging options for this subnetwork. If logging is enabled, logs are exported to Cloud Logging."
},
"metadata": {
"description": "Can only be specified if VPC flow logging for this subnetwork is enabled. Configures whether metadata fields should be added to the reported VPC flow logs. Options are INCLUDE_ALL_METADATA, EXCLUDE_ALL_METADATA, and CUSTOM_METADATA. Default is INCLUDE_ALL_METADATA.",
"description": "Can only be specified if VPC flow logging for this subnetwork is enabled. Configures whether metadata fields should be added to the reported VPC flow logs. Options are INCLUDE_ALL_METADATA, EXCLUDE_ALL_METADATA, and CUSTOM_METADATA. Default is EXCLUDE_ALL_METADATA.",
"enum": [
"EXCLUDE_ALL_METADATA",
"INCLUDE_ALL_METADATA"
Expand Down Expand Up @@ -66420,7 +66420,7 @@
"type": "number"
},
"metadata": {
"description": "Can only be specified if VPC flow logs for this subnetwork is enabled. Configures whether all, none or a subset of metadata fields should be added to the reported VPC flow logs. Default is INCLUDE_ALL_METADATA.",
"description": "Can only be specified if VPC flow logs for this subnetwork is enabled. Configures whether all, none or a subset of metadata fields should be added to the reported VPC flow logs. Default is EXCLUDE_ALL_METADATA.",
"enum": [
"CUSTOM_METADATA",
"EXCLUDE_ALL_METADATA",
Expand Down Expand Up @@ -71055,7 +71055,7 @@
"type": "integer"
},
"interconnectAttachment": {
"description": "URL of the interconnect attachment resource. When the value of this field is present, the VPN Gateway will be used for IPsec-encrypted Cloud Interconnect; all Egress or Ingress traffic for this VPN Gateway interface will go through the specified interconnect attachment resource.",
"description": "URL of the interconnect attachment resource. When the value of this field is present, the VPN Gateway will be used for IPsec-encrypted Cloud Interconnect; all Egress or Ingress traffic for this VPN Gateway interface will go through the specified interconnect attachment resource.\nNot currently available in all Interconnect locations.",
"type": "string"
},
"ipAddress": {
Expand Down Expand Up @@ -71277,7 +71277,7 @@
"type": "string"
},
"status": {
"description": "[Output Only] The status of the VPN tunnel, which can be one of the following: \n- PROVISIONING: Resource is being allocated for the VPN tunnel. \n- WAITING_FOR_FULL_CONFIG: Waiting to receive all VPN-related configs from the user. Network, TargetVpnGateway, VpnTunnel, ForwardingRule, and Route resources are needed to setup the VPN tunnel. \n- FIRST_HANDSHAKE: Successful first handshake with the peer VPN. \n- ESTABLISHED: Secure session is successfully established with the peer VPN. \n- NETWORK_ERROR: Deprecated, replaced by NO_INCOMING_PACKETS \n- AUTHORIZATION_ERROR: Auth error (for example, bad shared secret). \n- NEGOTIATION_FAILURE: Handshake failed. \n- DEPROVISIONING: Resources are being deallocated for the VPN tunnel. \n- FAILED: Tunnel creation has failed and the tunnel is not ready to be used. \n- NO_INCOMING_PACKETS: No incoming packets from peer. \n- REJECTED: Tunnel configuration was rejected, can be result of being blacklisted. \n- ALLOCATING_RESOURCES: Cloud VPN is in the process of allocating all required resources. \n- STOPPED: Tunnel is stopped due to its Forwarding Rules being deleted for Classic VPN tunnels or the project is in frozen state. \n- PEER_IDENTITY_MISMATCH: Peer identity does not match peer IP, probably behind NAT. \n- TS_NARROWING_NOT_ALLOWED: Traffic selector narrowing not allowed for an HA-VPN tunnel.",
"description": "[Output Only] The status of the VPN tunnel, which can be one of the following: \n- PROVISIONING: Resource is being allocated for the VPN tunnel. \n- WAITING_FOR_FULL_CONFIG: Waiting to receive all VPN-related configs from the user. Network, TargetVpnGateway, VpnTunnel, ForwardingRule, and Route resources are needed to setup the VPN tunnel. \n- FIRST_HANDSHAKE: Successful first handshake with the peer VPN. \n- ESTABLISHED: Secure session is successfully established with the peer VPN. \n- NETWORK_ERROR: Deprecated, replaced by NO_INCOMING_PACKETS \n- AUTHORIZATION_ERROR: Auth error (for example, bad shared secret). \n- NEGOTIATION_FAILURE: Handshake failed. \n- DEPROVISIONING: Resources are being deallocated for the VPN tunnel. \n- FAILED: Tunnel creation has failed and the tunnel is not ready to be used. \n- NO_INCOMING_PACKETS: No incoming packets from peer. \n- REJECTED: Tunnel configuration was rejected, can be result of being denied access. \n- ALLOCATING_RESOURCES: Cloud VPN is in the process of allocating all required resources. \n- STOPPED: Tunnel is stopped due to its Forwarding Rules being deleted for Classic VPN tunnels or the project is in frozen state. \n- PEER_IDENTITY_MISMATCH: Peer identity does not match peer IP, probably behind NAT. \n- TS_NARROWING_NOT_ALLOWED: Traffic selector narrowing not allowed for an HA-VPN tunnel.",
"enum": [
"ALLOCATING_RESOURCES",
"AUTHORIZATION_ERROR",
Expand Down

0 comments on commit 0d7e3fb

Please sign in to comment.