Update interconnect attachment encryption field

Changed description
GoogleCloudPlatform · Mar 3, 2023 · 2c01662 · 2c01662
1 parent f42899a
commit 2c01662
Showing 1 changed file with 12 additions and 13 deletions.
diff --git a/mmv1/products/compute/api.yaml b/mmv1/products/compute/api.yaml
@@ -7935,19 +7935,18 @@ objects:
         name: 'encryption'
         description: |
           Indicates the user-supplied encryption option of this interconnect
-          attachment:
-
-          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.
-
-          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.
+          attachment. Can only be specified at attachment creation for PARTNER
+          or DEDICATED attachments.
+
+          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 - 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