Compute interconnect attachment ha

mmv1/products/compute/Address.yaml

@@ -102,25 +102,26 @@ properties:
       except the last character, which cannot be a dash.
     required: true
   - !ruby/object:Api::Type::String
-    name: purpose
+    name: 'purpose'
     description: |
-      The purpose of this resource, which can be one of the following values:
+      The purpose of this resource, which can be one of the following values.
 
       * GCE_ENDPOINT for addresses that are used by VM instances, alias IP
-        ranges, internal load balancers, and similar resources.
+      ranges, load balancers, and similar resources.
 
       * SHARED_LOADBALANCER_VIP for an address that can be used by multiple
-        internal load balancers.
+      internal load balancers.
 
       * VPC_PEERING for addresses that are reserved for VPC peer networks.
 
-      * IPSEC_INTERCONNECT for addresses created from a private IP range
-        that are reserved for a VLAN attachment in an IPsec-encrypted Cloud
-        Interconnect configuration. These addresses are regional resources.
+      * IPSEC_INTERCONNECT for addresses created from a private IP range that
+      are reserved for a VLAN attachment in an HA VPN over Cloud Interconnect
+      configuration. These addresses are regional resources.
+
+      * PRIVATE_SERVICE_CONNECT for a private network address that is used to
+      configure Private Service Connect. Only global internal addresses can use
+      this purpose.
 
-      * PRIVATE_SERVICE_CONNECT for a private network address that is used
-      to configure Private Service Connect. Only global internal addresses
-      can use this purpose.
 
       This should only be set when using an Internal address.
   - !ruby/object:Api::Type::Enum

mmv1/products/compute/InterconnectAttachment.yaml

@@ -230,24 +230,23 @@ properties:
   - !ruby/object:Api::Type::Array
     name: '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.
+      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.
+      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.
+      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
+      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.
     input: true
     item_type: !ruby/object:Api::Type::ResourceRef
@@ -261,19 +260,18 @@ properties:
     name: 'encryption'
     description: |
       Indicates the user-supplied encryption option of this interconnect
-      attachment:
+      attachment. Can only be specified at attachment creation for PARTNER or
+      DEDICATED attachments.
 
-      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.
+      * NONE - This is the default value, which means that the VLAN attachment
+      carries unencrypted traffic. VMs are able to send traffic to, or receive
+      traffic from, such a VLAN attachment.
 
-      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.
-
-      Not currently available publicly.
+      * IPSEC - The VLAN attachment carries only encrypted traffic that is
+      encrypted by an IPsec device, such as an HA VPN gateway or third-party
+      IPsec VPN. VMs cannot directly send traffic to, or receive traffic from,
+      such a VLAN attachment. To use HA VPN over Cloud Interconnect, the VLAN
+      attachment must be created with this option.
     input: true
     values:
       - :NONE

mmv1/products/compute/Router.yaml

@@ -153,17 +153,20 @@ properties:
       - !ruby/object:Api::Type::Integer
         name: keepaliveInterval
         description: |
-          The interval in seconds between BGP keepalive messages that are sent to the peer.
-          Hold time is three times the interval at which keepalive messages are sent, and the hold time is the
-          maximum number of seconds allowed to elapse between successive keepalive messages that BGP receives from a peer.
-          BGP will use the smaller of either the local hold time value or the peer's hold time value as the hold time for
-          the BGP connection between the two peers. If set, this value must be between 20 and 60. The default is 20.
+          The interval in seconds between BGP keepalive messages that are sent
+          to the peer. Hold time is three times the interval at which keepalive
+          messages are sent, and the hold time is the maximum number of seconds
+          allowed to elapse between successive keepalive messages that BGP
+          receives from a peer.
+
+          BGP will use the smaller of either the local hold time value or the
+          peer's hold time value as the hold time for the BGP connection
+          between the two peers. If set, this value must be between 20 and 60.
+          The default is 20.
         default_value: 20
   - !ruby/object:Api::Type::Boolean
     name: encryptedInterconnectRouter
     input: true
     description: |
-      Field to indicate if a router is dedicated to use with encrypted
-      Interconnect Attachment (IPsec-encrypted Cloud Interconnect feature).
-
-      Not currently available publicly.
+      Indicates if a router is dedicated for use with encrypted VLAN
+      attachments (interconnectAttachments).