chore: Update discovery artifacts (#1328)
## Deleted keys were detected in the following stable discovery artifacts:
admindirectoryv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/1feda6f78f168e28d7842f49ad91fb00dc24ec19)
bigqueryreservationv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
computev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
doubleclickbidmanagerv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
doubleclickbidmanagerv11[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
serviceconsumermanagementv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceusagev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
## Deleted keys were detected in the following pre-stable discovery artifacts:
bigqueryreservationv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
computealpha[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
computebeta[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
serviceconsumermanagementv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceusagev1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
## Discovery Artifact Change Summary:
admindirectoryv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/1feda6f78f168e28d7842f49ad91fb00dc24ec19)
bigqueryreservationv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
bigqueryreservationv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/7e6c78d448e472caaa67971160fdd44ccce061b0)
computealpha[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
computebeta[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
computev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/131a5cd5bda8512217aa461042b33fb287790839)
containerv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9bc4a12e7ab57a1b5a5d3637087b80b3008e3352)
containerv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/9bc4a12e7ab57a1b5a5d3637087b80b3008e3352)
doubleclickbidmanagerv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
doubleclickbidmanagerv11[ [More details]](https://github.com/googleapis/google-api-python-client/commit/d20e7e2553a1ea5d3690afba366683d4eb0ca647)
serviceconsumermanagementv1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceconsumermanagementv1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/864ef4795a0e89263859f493f9c40d1a85e90c28)
serviceusagev1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
serviceusagev1beta1[ [More details]](https://github.com/googleapis/google-api-python-client/commit/ecd65a89c54132856b47747439faf901dbfbafcb)
diff --git a/docs/dyn/compute_beta.interconnectAttachments.html b/docs/dyn/compute_beta.interconnectAttachments.html
index 113bcfb..05e96cf 100644
--- a/docs/dyn/compute_beta.interconnectAttachments.html
+++ b/docs/dyn/compute_beta.interconnectAttachments.html
@@ -175,7 +175,7 @@
"googleReferenceId": "A String", # [Output Only] Google reference ID, to be used when raising support tickets with Google or otherwise to debug backend connectivity issues. [Deprecated] This field is not used.
"id": "A String", # [Output Only] The unique identifier for the resource. This identifier is defined by the server.
"interconnect": "A String", # URL of the underlying Interconnect object that this attachment's traffic will traverse through.
- "ipsecInternalAddresses": [ # 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.
+ "ipsecInternalAddresses": [ # 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.
# Not currently available in all Interconnect locations.
"A String",
],
@@ -396,7 +396,7 @@
"googleReferenceId": "A String", # [Output Only] Google reference ID, to be used when raising support tickets with Google or otherwise to debug backend connectivity issues. [Deprecated] This field is not used.
"id": "A String", # [Output Only] The unique identifier for the resource. This identifier is defined by the server.
"interconnect": "A String", # URL of the underlying Interconnect object that this attachment's traffic will traverse through.
- "ipsecInternalAddresses": [ # 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.
+ "ipsecInternalAddresses": [ # 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.
# Not currently available in all Interconnect locations.
"A String",
],
@@ -486,7 +486,7 @@
"googleReferenceId": "A String", # [Output Only] Google reference ID, to be used when raising support tickets with Google or otherwise to debug backend connectivity issues. [Deprecated] This field is not used.
"id": "A String", # [Output Only] The unique identifier for the resource. This identifier is defined by the server.
"interconnect": "A String", # URL of the underlying Interconnect object that this attachment's traffic will traverse through.
- "ipsecInternalAddresses": [ # 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.
+ "ipsecInternalAddresses": [ # 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.
# Not currently available in all Interconnect locations.
"A String",
],
@@ -665,7 +665,7 @@
"googleReferenceId": "A String", # [Output Only] Google reference ID, to be used when raising support tickets with Google or otherwise to debug backend connectivity issues. [Deprecated] This field is not used.
"id": "A String", # [Output Only] The unique identifier for the resource. This identifier is defined by the server.
"interconnect": "A String", # URL of the underlying Interconnect object that this attachment's traffic will traverse through.
- "ipsecInternalAddresses": [ # 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.
+ "ipsecInternalAddresses": [ # 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.
# Not currently available in all Interconnect locations.
"A String",
],
@@ -786,7 +786,7 @@
"googleReferenceId": "A String", # [Output Only] Google reference ID, to be used when raising support tickets with Google or otherwise to debug backend connectivity issues. [Deprecated] This field is not used.
"id": "A String", # [Output Only] The unique identifier for the resource. This identifier is defined by the server.
"interconnect": "A String", # URL of the underlying Interconnect object that this attachment's traffic will traverse through.
- "ipsecInternalAddresses": [ # 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.
+ "ipsecInternalAddresses": [ # 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.
# Not currently available in all Interconnect locations.
"A String",
],