oci-vnmonitoring 2.76.1 → 2.77.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (212) hide show
  1. package/lib/client.d.ts +12 -12
  2. package/lib/client.js +12 -12
  3. package/lib/model/add-drg-route-rule-details.d.ts +3 -3
  4. package/lib/model/add-public-ip-pool-capacity-details.d.ts +3 -3
  5. package/lib/model/add-security-rule-details.d.ts +21 -21
  6. package/lib/model/add-subnet-ipv6-cidr-details.d.ts +1 -1
  7. package/lib/model/add-vcn-ipv6-cidr-details.d.ts +1 -1
  8. package/lib/model/bgp-session-info.d.ts +15 -15
  9. package/lib/model/byoip-allocated-range-collection.d.ts +1 -1
  10. package/lib/model/byoip-range-collection.d.ts +2 -2
  11. package/lib/model/byoip-range-summary.d.ts +9 -9
  12. package/lib/model/byoip-range-vcn-ipv6-allocation-summary.d.ts +3 -3
  13. package/lib/model/byoip-range.d.ts +15 -15
  14. package/lib/model/byoipv6-cidr-details.d.ts +3 -3
  15. package/lib/model/capture-filter.d.ts +3 -3
  16. package/lib/model/change-path-analyzer-test-compartment-details.d.ts +2 -2
  17. package/lib/model/compute-instance-endpoint.d.ts +2 -2
  18. package/lib/model/connect-remote-peering-connections-details.d.ts +1 -1
  19. package/lib/model/cpe-device-config-answer.d.ts +2 -2
  20. package/lib/model/cpe.d.ts +5 -5
  21. package/lib/model/create-byoip-range-details.d.ts +4 -4
  22. package/lib/model/create-capture-filter-details.d.ts +2 -2
  23. package/lib/model/create-cpe-details.d.ts +4 -4
  24. package/lib/model/create-cross-connect-details.d.ts +4 -4
  25. package/lib/model/create-cross-connect-group-details.d.ts +2 -2
  26. package/lib/model/create-dhcp-details.d.ts +2 -2
  27. package/lib/model/create-drg-attachment-details.d.ts +3 -3
  28. package/lib/model/create-drg-details.d.ts +2 -2
  29. package/lib/model/create-drg-route-distribution-details.d.ts +2 -2
  30. package/lib/model/create-drg-route-table-details.d.ts +2 -2
  31. package/lib/model/create-internet-gateway-details.d.ts +2 -2
  32. package/lib/model/create-ip-sec-connection-details.d.ts +12 -12
  33. package/lib/model/create-ip-sec-connection-tunnel-details.d.ts +3 -3
  34. package/lib/model/create-ip-sec-tunnel-bgp-session-details.d.ts +15 -15
  35. package/lib/model/create-ipv6-details.d.ts +4 -4
  36. package/lib/model/create-local-peering-gateway-details.d.ts +2 -2
  37. package/lib/model/create-nat-gateway-details.d.ts +4 -4
  38. package/lib/model/create-network-security-group-details.d.ts +2 -2
  39. package/lib/model/create-path-analyzer-test-details.d.ts +5 -5
  40. package/lib/model/create-private-ip-details.d.ts +5 -5
  41. package/lib/model/create-public-ip-details.d.ts +2 -2
  42. package/lib/model/create-public-ip-pool-details.d.ts +2 -2
  43. package/lib/model/create-remote-peering-connection-details.d.ts +2 -2
  44. package/lib/model/create-route-table-details.d.ts +2 -2
  45. package/lib/model/create-security-list-details.d.ts +2 -2
  46. package/lib/model/create-service-gateway-details.d.ts +4 -4
  47. package/lib/model/create-subnet-details.d.ts +14 -14
  48. package/lib/model/create-vcn-details.d.ts +11 -11
  49. package/lib/model/create-virtual-circuit-details.d.ts +13 -13
  50. package/lib/model/create-vlan-details.d.ts +4 -4
  51. package/lib/model/create-vnic-details.d.ts +24 -24
  52. package/lib/model/create-vtap-details.d.ts +7 -7
  53. package/lib/model/cross-connect-group.d.ts +4 -4
  54. package/lib/model/cross-connect-location.d.ts +1 -1
  55. package/lib/model/cross-connect-mapping-details.d.ts +6 -6
  56. package/lib/model/cross-connect-mapping.d.ts +7 -7
  57. package/lib/model/cross-connect-port-speed-shape.d.ts +2 -2
  58. package/lib/model/cross-connect-status.d.ts +2 -2
  59. package/lib/model/cross-connect.d.ts +5 -5
  60. package/lib/model/dhcp-dns-option.d.ts +1 -1
  61. package/lib/model/dhcp-options.d.ts +3 -3
  62. package/lib/model/dhcp-search-domain-option.d.ts +2 -2
  63. package/lib/model/drg-attachment-info.d.ts +1 -1
  64. package/lib/model/drg-attachment.d.ts +6 -6
  65. package/lib/model/drg-route-distribution-statement.d.ts +1 -1
  66. package/lib/model/drg-route-distribution.d.ts +4 -4
  67. package/lib/model/drg-route-rule.d.ts +10 -10
  68. package/lib/model/drg-route-table.d.ts +4 -4
  69. package/lib/model/drg.d.ts +3 -3
  70. package/lib/model/egress-security-rule.d.ts +9 -9
  71. package/lib/model/endpoint.d.ts +1 -1
  72. package/lib/model/fast-connect-provider-service-key.d.ts +2 -2
  73. package/lib/model/fast-connect-provider-service.d.ts +1 -1
  74. package/lib/model/flow-log-capture-filter-rule-details.d.ts +1 -1
  75. package/lib/model/i-psec-connection-device-status.d.ts +1 -1
  76. package/lib/model/i-psec-connection-tunnel.d.ts +7 -7
  77. package/lib/model/i-psec-connection.d.ts +14 -14
  78. package/lib/model/icmp-traffic-protocol-parameters.d.ts +1 -1
  79. package/lib/model/ingress-security-rule.d.ts +9 -9
  80. package/lib/model/internet-gateway.d.ts +3 -3
  81. package/lib/model/ip-address-endpoint.d.ts +2 -2
  82. package/lib/model/ipv6.d.ts +7 -7
  83. package/lib/model/letter-of-authority.d.ts +1 -1
  84. package/lib/model/load-balancer-endpoint.d.ts +1 -1
  85. package/lib/model/load-balancer-listener-endpoint.d.ts +1 -1
  86. package/lib/model/local-peering-gateway.d.ts +11 -11
  87. package/lib/model/macsec-key.d.ts +1 -1
  88. package/lib/model/nat-gateway.d.ts +5 -5
  89. package/lib/model/network-load-balancer-endpoint.d.ts +1 -1
  90. package/lib/model/network-load-balancer-listener-endpoint.d.ts +1 -1
  91. package/lib/model/network-security-group-vnic.d.ts +1 -1
  92. package/lib/model/network-security-group.d.ts +3 -3
  93. package/lib/model/path-analysis-work-request-result.d.ts +2 -2
  94. package/lib/model/path-analyzer-test-collection.d.ts +2 -2
  95. package/lib/model/path-analyzer-test-summary.d.ts +9 -9
  96. package/lib/model/path-analyzer-test.d.ts +9 -9
  97. package/lib/model/path.d.ts +1 -1
  98. package/lib/model/persisted-get-path-analysis-details.d.ts +2 -2
  99. package/lib/model/private-ip.d.ts +21 -21
  100. package/lib/model/protocol-parameters.d.ts +1 -1
  101. package/lib/model/public-ip-pool-collection.d.ts +1 -1
  102. package/lib/model/public-ip-pool-summary.d.ts +3 -3
  103. package/lib/model/public-ip-pool.d.ts +3 -3
  104. package/lib/model/public-ip.d.ts +17 -17
  105. package/lib/model/query-options.d.ts +1 -1
  106. package/lib/model/remote-peering-connection.d.ts +7 -7
  107. package/lib/model/remove-public-ip-pool-capacity-details.d.ts +1 -1
  108. package/lib/model/remove-subnet-ipv6-cidr-details.d.ts +1 -1
  109. package/lib/model/remove-vcn-ipv6-cidr-details.d.ts +1 -1
  110. package/lib/model/route-rule.d.ts +13 -13
  111. package/lib/model/route-table.d.ts +4 -4
  112. package/lib/model/security-action.d.ts +1 -1
  113. package/lib/model/security-list.d.ts +3 -3
  114. package/lib/model/security-rule.d.ts +26 -26
  115. package/lib/model/service-gateway.d.ts +7 -7
  116. package/lib/model/service.d.ts +10 -10
  117. package/lib/model/subnet-endpoint.d.ts +2 -2
  118. package/lib/model/subnet.d.ts +21 -21
  119. package/lib/model/tcp-protocol-parameters.d.ts +2 -2
  120. package/lib/model/tcp-traffic-protocol-parameters.d.ts +3 -3
  121. package/lib/model/topology-associated-with-entity-relationship.d.ts +2 -2
  122. package/lib/model/topology-associated-with-relationship-details.d.ts +1 -1
  123. package/lib/model/topology-contains-entity-relationship.d.ts +2 -2
  124. package/lib/model/topology-routes-to-entity-relationship.d.ts +1 -1
  125. package/lib/model/topology-routes-to-relationship-details.d.ts +5 -5
  126. package/lib/model/topology.d.ts +1 -1
  127. package/lib/model/traffic-node.d.ts +1 -1
  128. package/lib/model/traffic-protocol-parameters.d.ts +1 -1
  129. package/lib/model/traffic-route.d.ts +1 -1
  130. package/lib/model/tunnel-config.d.ts +2 -2
  131. package/lib/model/tunnel-cpe-device-config.d.ts +1 -1
  132. package/lib/model/tunnel-phase-one-details.d.ts +1 -1
  133. package/lib/model/tunnel-phase-two-details.d.ts +1 -1
  134. package/lib/model/tunnel-security-association-summary.d.ts +1 -1
  135. package/lib/model/tunnel-status.d.ts +3 -3
  136. package/lib/model/udp-protocol-parameters.d.ts +2 -2
  137. package/lib/model/udp-traffic-protocol-parameters.d.ts +3 -3
  138. package/lib/model/update-byoip-range-details.d.ts +3 -3
  139. package/lib/model/update-capture-filter-details.d.ts +2 -2
  140. package/lib/model/update-cpe-details.d.ts +2 -2
  141. package/lib/model/update-cross-connect-details.d.ts +3 -3
  142. package/lib/model/update-cross-connect-group-details.d.ts +2 -2
  143. package/lib/model/update-dhcp-details.d.ts +2 -2
  144. package/lib/model/update-drg-attachment-details.d.ts +2 -2
  145. package/lib/model/update-drg-details.d.ts +2 -2
  146. package/lib/model/update-drg-route-distribution-details.d.ts +2 -2
  147. package/lib/model/update-drg-route-rule-details.d.ts +3 -3
  148. package/lib/model/update-drg-route-table-details.d.ts +2 -2
  149. package/lib/model/update-internet-gateway-details.d.ts +2 -2
  150. package/lib/model/update-ip-sec-connection-details.d.ts +8 -8
  151. package/lib/model/update-ip-sec-connection-tunnel-details.d.ts +3 -3
  152. package/lib/model/update-ip-sec-tunnel-bgp-session-details.d.ts +16 -16
  153. package/lib/model/update-ipv6-details.d.ts +2 -2
  154. package/lib/model/update-local-peering-gateway-details.d.ts +2 -2
  155. package/lib/model/update-nat-gateway-details.d.ts +4 -4
  156. package/lib/model/update-network-security-group-details.d.ts +2 -2
  157. package/lib/model/update-path-analyzer-test-details.d.ts +4 -4
  158. package/lib/model/update-private-ip-details.d.ts +4 -4
  159. package/lib/model/update-public-ip-details.d.ts +2 -2
  160. package/lib/model/update-public-ip-pool-details.d.ts +2 -2
  161. package/lib/model/update-remote-peering-connection-details.d.ts +2 -2
  162. package/lib/model/update-route-table-details.d.ts +2 -2
  163. package/lib/model/update-security-list-details.d.ts +2 -2
  164. package/lib/model/update-security-rule-details.d.ts +23 -23
  165. package/lib/model/update-service-gateway-details.d.ts +8 -8
  166. package/lib/model/update-subnet-details.d.ts +5 -5
  167. package/lib/model/update-vcn-details.d.ts +2 -2
  168. package/lib/model/update-virtual-circuit-details.d.ts +7 -7
  169. package/lib/model/update-vlan-details.d.ts +3 -3
  170. package/lib/model/update-vnic-details.d.ts +7 -7
  171. package/lib/model/update-vtap-details.d.ts +5 -5
  172. package/lib/model/upgrade-status.d.ts +1 -1
  173. package/lib/model/vcn.d.ts +8 -8
  174. package/lib/model/virtual-circuit-bandwidth-shape.d.ts +2 -2
  175. package/lib/model/virtual-circuit-drg-attachment-network-details.d.ts +1 -1
  176. package/lib/model/virtual-circuit-public-prefix.d.ts +2 -2
  177. package/lib/model/virtual-circuit.d.ts +11 -11
  178. package/lib/model/vlan-endpoint.d.ts +2 -2
  179. package/lib/model/vlan.d.ts +6 -6
  180. package/lib/model/vnic-endpoint.d.ts +2 -2
  181. package/lib/model/vnic.d.ts +16 -16
  182. package/lib/model/vtap.d.ts +8 -8
  183. package/lib/model/work-request-error-collection.d.ts +2 -2
  184. package/lib/model/work-request-log-entry-collection.d.ts +1 -1
  185. package/lib/model/work-request-resource.d.ts +3 -3
  186. package/lib/model/work-request-result-collection.d.ts +2 -2
  187. package/lib/model/work-request-summary-collection.d.ts +2 -2
  188. package/lib/model/work-request-summary.d.ts +2 -2
  189. package/lib/model/work-request.d.ts +2 -2
  190. package/lib/request/change-path-analyzer-test-compartment-request.d.ts +3 -3
  191. package/lib/request/create-path-analyzer-test-request.d.ts +1 -1
  192. package/lib/request/delete-path-analyzer-test-request.d.ts +3 -3
  193. package/lib/request/get-path-analysis-request.d.ts +1 -1
  194. package/lib/request/get-path-analyzer-test-request.d.ts +2 -2
  195. package/lib/request/get-work-request-request.d.ts +1 -1
  196. package/lib/request/list-path-analyzer-tests-request.d.ts +7 -7
  197. package/lib/request/list-work-request-errors-request.d.ts +5 -5
  198. package/lib/request/list-work-request-logs-request.d.ts +5 -5
  199. package/lib/request/list-work-request-results-request.d.ts +3 -3
  200. package/lib/request/list-work-requests-request.d.ts +6 -6
  201. package/lib/request/update-path-analyzer-test-request.d.ts +3 -3
  202. package/lib/response/change-path-analyzer-test-compartment-response.d.ts +1 -1
  203. package/lib/response/create-path-analyzer-test-response.d.ts +1 -1
  204. package/lib/response/get-path-analyzer-test-response.d.ts +1 -1
  205. package/lib/response/get-work-request-response.d.ts +1 -1
  206. package/lib/response/list-path-analyzer-tests-response.d.ts +1 -1
  207. package/lib/response/list-work-request-errors-response.d.ts +1 -1
  208. package/lib/response/list-work-request-logs-response.d.ts +1 -1
  209. package/lib/response/list-work-request-results-response.d.ts +1 -1
  210. package/lib/response/list-work-requests-response.d.ts +1 -1
  211. package/lib/response/update-path-analyzer-test-response.d.ts +1 -1
  212. package/package.json +3 -3
@@ -46,7 +46,7 @@ export interface DrgAttachment {
46
46
  /**
47
47
  * The date and time the DRG attachment was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
48
48
  * <p>
49
- Example: `2016-08-25T21:10:29.600Z`
49
+ Example: {@code 2016-08-25T21:10:29.600Z}
50
50
  *
51
51
  */
52
52
  "timeCreated"?: Date;
@@ -60,7 +60,7 @@ export interface DrgAttachment {
60
60
  "networkDetails"?: model.VcnDrgAttachmentNetworkDetails | model.LoopBackDrgAttachmentNetworkDetails | model.IpsecTunnelDrgAttachmentNetworkDetails | model.VirtualCircuitDrgAttachmentNetworkDetails | model.RemotePeeringConnectionDrgAttachmentNetworkDetails;
61
61
  /**
62
62
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
63
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
63
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
64
64
  *
65
65
  */
66
66
  "definedTags"?: {
@@ -70,7 +70,7 @@ export interface DrgAttachment {
70
70
  };
71
71
  /**
72
72
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
73
- * Example: `{\"bar-key\": \"value\"}`
73
+ * Example: {@code {\"bar-key\": \"value\"}}
74
74
  *
75
75
  */
76
76
  "freeformTags"?: {
@@ -84,13 +84,13 @@ export interface DrgAttachment {
84
84
  * [Transit Routing: Access to Multiple VCNs in Same Region](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/transitrouting.htm)
85
85
  * * [Transit Routing: Private Access to Oracle Services](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/transitroutingoracleservices.htm)
86
86
  * <p>
87
- This field is deprecated. Instead, use the `networkDetails` field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
87
+ This field is deprecated. Instead, use the {@code networkDetails} field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
88
88
  *
89
89
  */
90
90
  "routeTableId"?: string;
91
91
  /**
92
92
  * The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the VCN.
93
- * This field is deprecated. Instead, use the `networkDetails` field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
93
+ * This field is deprecated. Instead, use the {@code networkDetails} field to view the [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the attached resource.
94
94
  *
95
95
  */
96
96
  "vcnId"?: string;
@@ -104,7 +104,7 @@ export interface DrgAttachment {
104
104
  /**
105
105
  * Indicates whether the DRG attachment and attached network live in a different tenancy than the DRG.
106
106
  * <p>
107
- Example: `false`
107
+ Example: {@code false}
108
108
  *
109
109
  */
110
110
  "isCrossTenancy"?: boolean;
@@ -26,7 +26,7 @@ export interface DrgRouteDistributionStatement {
26
26
  */
27
27
  "matchCriteria": Array<model.DrgRouteDistributionMatchCriteria>;
28
28
  /**
29
- * `ACCEPT` indicates the route should be imported or exported as-is.
29
+ * {@code ACCEPT} indicates the route should be imported or exported as-is.
30
30
  *
31
31
  */
32
32
  "action": DrgRouteDistributionStatement.Action;
@@ -15,7 +15,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
15
15
  /**
16
16
  * A route distribution establishes how routes get imported into DRG route tables and exported through the DRG attachments.
17
17
  * <p>
18
- A route distribution is a list of statements. Each statement consists of a set of matches, all of which must be `True` in order for
18
+ A route distribution is a list of statements. Each statement consists of a set of matches, all of which must be {@code True} in order for
19
19
  * the statement's action to take place. Each statement determines which routes are propagated.
20
20
  * <p>
21
21
  You can assign a route distribution as a route table's import distribution. The statements in an import
@@ -48,7 +48,7 @@ export interface DrgRouteDistribution {
48
48
  "compartmentId": string;
49
49
  /**
50
50
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
51
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
51
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
52
52
  *
53
53
  */
54
54
  "definedTags"?: {
@@ -64,7 +64,7 @@ export interface DrgRouteDistribution {
64
64
  "displayName"?: string;
65
65
  /**
66
66
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
67
- * Example: `{\"bar-key\": \"value\"}`
67
+ * Example: {@code {\"bar-key\": \"value\"}}
68
68
  *
69
69
  */
70
70
  "freeformTags"?: {
@@ -81,7 +81,7 @@ export interface DrgRouteDistribution {
81
81
  /**
82
82
  * The date and time the route distribution was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
83
83
  * <p>
84
- Example: `2016-08-25T21:10:29.600Z`
84
+ Example: {@code 2016-08-25T21:10:29.600Z}
85
85
  *
86
86
  */
87
87
  "timeCreated": Date;
@@ -23,10 +23,10 @@ export interface DrgRouteRule {
23
23
  * Represents the range of IP addresses to match against when routing traffic.
24
24
  * <p>
25
25
  Potential values:
26
- * * An IP address range (IPv4 or IPv6) in CIDR notation. For example: `192.168.1.0/24`
27
- * or `2001:0db8:0123:45::/56`.
28
- * * When you're setting up a security rule for traffic destined for a particular `Service` through
29
- * a service gateway, this is the `cidrBlock` value associated with that {@link Service}. For example: `oci-phx-objectstorage`.
26
+ * * An IP address range (IPv4 or IPv6) in CIDR notation. For example: {@code 192.168.1.0/24}
27
+ * or {@code 2001:0db8:0123:45::/56}.
28
+ * * When you're setting up a security rule for traffic destined for a particular {@code Service} through
29
+ * a service gateway, this is the {@code cidrBlock} value associated with that {@link Service}. For example: {@code oci-phx-objectstorage}.
30
30
  *
31
31
  */
32
32
  "destination": string;
@@ -35,10 +35,10 @@ export interface DrgRouteRule {
35
35
  * <p>
36
36
  Allowed values:
37
37
  * <p>
38
- * `CIDR_BLOCK`: If the rule's `destination` is an IP address range in CIDR notation.
39
- * * `SERVICE_CIDR_BLOCK`: If the rule's `destination` is the `cidrBlock` value for a
38
+ * {@code CIDR_BLOCK}: If the rule's {@code destination} is an IP address range in CIDR notation.
39
+ * * {@code SERVICE_CIDR_BLOCK}: If the rule's {@code destination} is the {@code cidrBlock} value for a
40
40
  * {@link Service} (the rule is for traffic destined for a
41
- * particular `Service` through a service gateway).
41
+ * particular {@code Service} through a service gateway).
42
42
  *
43
43
  */
44
44
  "destinationType": DrgRouteRule.DestinationType;
@@ -46,7 +46,7 @@ export interface DrgRouteRule {
46
46
  * The [OCID](https://docs.cloud.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the next hop DRG attachment responsible
47
47
  * for reaching the network destination.
48
48
  * <p>
49
- A value of `BLACKHOLE` means traffic for this route is discarded without notification.
49
+ A value of {@code BLACKHOLE} means traffic for this route is discarded without notification.
50
50
  *
51
51
  */
52
52
  "nextHopDrgAttachmentId": string;
@@ -73,10 +73,10 @@ export interface DrgRouteRule {
73
73
  "id": string;
74
74
  /**
75
75
  * The earliest origin of a route. If a route is advertised to a DRG through an IPsec tunnel attachment,
76
- * and is propagated to peered DRGs via RPC attachments, the route's provenance in the peered DRGs remains `IPSEC_TUNNEL`,
76
+ * and is propagated to peered DRGs via RPC attachments, the route's provenance in the peered DRGs remains {@code IPSEC_TUNNEL},
77
77
  * because that is the earliest origin.
78
78
  * <p>
79
- No routes with a provenance `IPSEC_TUNNEL` or `VIRTUAL_CIRCUIT` will be exported to IPsec tunnel or virtual circuit attachments,
79
+ No routes with a provenance {@code IPSEC_TUNNEL} or {@code VIRTUAL_CIRCUIT} will be exported to IPsec tunnel or virtual circuit attachments,
80
80
  * regardless of the attachment's export distribution.
81
81
  *
82
82
  */
@@ -19,7 +19,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
19
19
  * The routing decision for a packet entering a DRG is determined by the rules in the DRG route table
20
20
  * assigned to the attachment-of-entry.
21
21
  * <p>
22
- Each DRG attachment can inject routes in any DRG route table, provided there is a statement corresponding to the attachment in the route table's `importDrgRouteDistribution`.
22
+ Each DRG attachment can inject routes in any DRG route table, provided there is a statement corresponding to the attachment in the route table's {@code importDrgRouteDistribution}.
23
23
  * You can also insert static routes into the DRG route tables.
24
24
  * <p>
25
25
  The DRG route table is always in the same compartment as the DRG. There must always be a default
@@ -46,7 +46,7 @@ export interface DrgRouteTable {
46
46
  "drgId": string;
47
47
  /**
48
48
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
49
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
49
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
50
50
  *
51
51
  */
52
52
  "definedTags"?: {
@@ -62,7 +62,7 @@ export interface DrgRouteTable {
62
62
  "displayName"?: string;
63
63
  /**
64
64
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
65
- * Example: `{\"bar-key\": \"value\"}`
65
+ * Example: {@code {\"bar-key\": \"value\"}}
66
66
  *
67
67
  */
68
68
  "freeformTags"?: {
@@ -71,7 +71,7 @@ export interface DrgRouteTable {
71
71
  /**
72
72
  * The date and time the DRG route table was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
73
73
  * <p>
74
- Example: `2016-08-25T21:10:29.600Z`
74
+ Example: {@code 2016-08-25T21:10:29.600Z}
75
75
  *
76
76
  */
77
77
  "timeCreated": Date;
@@ -32,7 +32,7 @@ export interface Drg {
32
32
  "compartmentId": string;
33
33
  /**
34
34
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
35
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
35
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
36
36
  *
37
37
  */
38
38
  "definedTags"?: {
@@ -48,7 +48,7 @@ export interface Drg {
48
48
  "displayName"?: string;
49
49
  /**
50
50
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
51
- * Example: `{\"bar-key\": \"value\"}`
51
+ * Example: {@code {\"bar-key\": \"value\"}}
52
52
  *
53
53
  */
54
54
  "freeformTags"?: {
@@ -65,7 +65,7 @@ export interface Drg {
65
65
  /**
66
66
  * The date and time the DRG was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
67
67
  * <p>
68
- Example: `2016-08-25T21:10:29.600Z`
68
+ Example: {@code 2016-08-25T21:10:29.600Z}
69
69
  *
70
70
  */
71
71
  "timeCreated"?: Date;
@@ -23,26 +23,26 @@ export interface EgressSecurityRule {
23
23
  * <p>
24
24
  Allowed values:
25
25
  * <p>
26
- * IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`
26
+ * IP address range in CIDR notation. For example: {@code 192.168.1.0/24} or {@code 2001:0db8:0123:45::/56}
27
27
  * Note that IPv6 addressing is currently supported only in certain regions. See
28
28
  * [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
29
29
  * <p>
30
- * The `cidrBlock` value for a {@link Service}, if you're
31
- * setting up a security list rule for traffic destined for a particular `Service` through
32
- * a service gateway. For example: `oci-phx-objectstorage`.
30
+ * The {@code cidrBlock} value for a {@link Service}, if you're
31
+ * setting up a security list rule for traffic destined for a particular {@code Service} through
32
+ * a service gateway. For example: {@code oci-phx-objectstorage}.
33
33
  *
34
34
  */
35
35
  "destination": string;
36
36
  /**
37
- * Type of destination for the rule. The default is `CIDR_BLOCK`.
37
+ * Type of destination for the rule. The default is {@code CIDR_BLOCK}.
38
38
  * <p>
39
39
  Allowed values:
40
40
  * <p>
41
- * `CIDR_BLOCK`: If the rule's `destination` is an IP address range in CIDR notation.
41
+ * {@code CIDR_BLOCK}: If the rule's {@code destination} is an IP address range in CIDR notation.
42
42
  * <p>
43
- * `SERVICE_CIDR_BLOCK`: If the rule's `destination` is the `cidrBlock` value for a
43
+ * {@code SERVICE_CIDR_BLOCK}: If the rule's {@code destination} is the {@code cidrBlock} value for a
44
44
  * {@link Service} (the rule is for traffic destined for a
45
- * particular `Service` through a service gateway).
45
+ * particular {@code Service} through a service gateway).
46
46
  *
47
47
  */
48
48
  "destinationType"?: EgressSecurityRule.DestinationType;
@@ -57,7 +57,7 @@ export interface EgressSecurityRule {
57
57
  */
58
58
  "isStateless"?: boolean;
59
59
  /**
60
- * The transport protocol. Specify either `all` or an IPv4 protocol number as
60
+ * The transport protocol. Specify either {@code all} or an IPv4 protocol number as
61
61
  * defined in
62
62
  * [Protocol Numbers](http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml).
63
63
  * Options are supported only for ICMP (\"1\"), TCP (\"6\"), UDP (\"17\"), and ICMPv6 (\"58\").
@@ -13,7 +13,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
13
13
  * This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
14
14
  */
15
15
  /**
16
- * Information describing a source or destination in a `PathAnalyzerTest` resource.
16
+ * Information describing a source or destination in a {@code PathAnalyzerTest} resource.
17
17
  *
18
18
  */
19
19
  export interface Endpoint {
@@ -20,7 +20,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
20
20
  export interface FastConnectProviderServiceKey {
21
21
  /**
22
22
  * The service key that the provider gives you when you set up a virtual circuit connection
23
- * from the provider to Oracle Cloud Infrastructure. Use this value as the `providerServiceKeyName`
23
+ * from the provider to Oracle Cloud Infrastructure. Use this value as the {@code providerServiceKeyName}
24
24
  * query parameter for
25
25
  * {@link #getFastConnectProviderServiceKey(GetFastConnectProviderServiceKeyRequest) getFastConnectProviderServiceKey}.
26
26
  *
@@ -31,7 +31,7 @@ export interface FastConnectProviderServiceKey {
31
31
  * available bandwidth levels (that is, shapes), see
32
32
  * {@link #listFastConnectProviderVirtualCircuitBandwidthShapes(ListFastConnectProviderVirtualCircuitBandwidthShapesRequest) listFastConnectProviderVirtualCircuitBandwidthShapes}.
33
33
  * <p>
34
- Example: `10 Gbps`
34
+ Example: {@code 10 Gbps}
35
35
  *
36
36
  */
37
37
  "bandwidthShapeName"?: string;
@@ -23,7 +23,7 @@ export interface FastConnectProviderService {
23
23
  * about the provider service, create a virtual circuit connection from the provider to Oracle
24
24
  * Cloud Infrastructure, and retrieve your provider service key for that virtual circuit connection.
25
25
  * <p>
26
- Example: `https://example.com`
26
+ Example: {@code https://example.com}
27
27
  *
28
28
  */
29
29
  "description"?: string;
@@ -52,7 +52,7 @@ export interface FlowLogCaptureFilterRuleDetails {
52
52
  "tcpOptions"?: model.TcpOptions;
53
53
  "udpOptions"?: model.UdpOptions;
54
54
  /**
55
- * Type or types of flow logs to store. `ALL` includes records for both accepted traffic and
55
+ * Type or types of flow logs to store. {@code ALL} includes records for both accepted traffic and
56
56
  * rejected traffic.
57
57
  *
58
58
  */
@@ -30,7 +30,7 @@ export interface IPSecConnectionDeviceStatus {
30
30
  /**
31
31
  * The date and time the IPSec connection was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
32
32
  * <p>
33
- Example: `2016-08-25T21:10:29.600Z`
33
+ Example: {@code 2016-08-25T21:10:29.600Z}
34
34
  *
35
35
  */
36
36
  "timeCreated"?: Date;
@@ -32,14 +32,14 @@ export interface IPSecConnectionTunnel {
32
32
  /**
33
33
  * The IP address of the Oracle VPN headend for the connection.
34
34
  * <p>
35
- Example: `203.0.113.21`
35
+ Example: {@code 203.0.113.21}
36
36
  *
37
37
  */
38
38
  "vpnIp"?: string;
39
39
  /**
40
40
  * The IP address of the CPE device's VPN headend.
41
41
  * <p>
42
- Example: `203.0.113.22`
42
+ Example: {@code 203.0.113.22}
43
43
  *
44
44
  */
45
45
  "cpeIp"?: string;
@@ -72,14 +72,14 @@ export interface IPSecConnectionTunnel {
72
72
  /**
73
73
  * The date and time the IPSec tunnel was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
74
74
  * <p>
75
- Example: `2016-08-25T21:10:29.600Z`
75
+ Example: {@code 2016-08-25T21:10:29.600Z}
76
76
  *
77
77
  */
78
78
  "timeCreated"?: Date;
79
79
  /**
80
80
  * When the status of the IPSec tunnel last changed, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
81
81
  * <p>
82
- Example: `2016-08-25T21:10:29.600Z`
82
+ Example: {@code 2016-08-25T21:10:29.600Z}
83
83
  *
84
84
  */
85
85
  "timeStatusUpdated"?: Date;
@@ -89,13 +89,13 @@ export interface IPSecConnectionTunnel {
89
89
  */
90
90
  "oracleCanInitiate"?: IPSecConnectionTunnel.OracleCanInitiate;
91
91
  /**
92
- * By default (the `AUTO` setting), IKE sends packets with a source and destination port set to 500,
92
+ * By default (the {@code AUTO} setting), IKE sends packets with a source and destination port set to 500,
93
93
  * and when it detects that the port used to forward packets has changed (most likely because a NAT device
94
94
  * is between the CPE device and the Oracle VPN headend) it will try to negotiate the use of NAT-T.
95
95
  * <p>
96
- The `ENABLED` option sets the IKE protocol to use port 4500 instead of 500 and forces encapsulating traffic with the ESP protocol inside UDP packets.
96
+ The {@code ENABLED} option sets the IKE protocol to use port 4500 instead of 500 and forces encapsulating traffic with the ESP protocol inside UDP packets.
97
97
  * <p>
98
- The `DISABLED` option directs IKE to completely refuse to negotiate NAT-T
98
+ The {@code DISABLED} option directs IKE to completely refuse to negotiate NAT-T
99
99
  * even if it senses there may be a NAT device in use.
100
100
  * <p>
101
101
 
@@ -19,14 +19,14 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
19
19
  * <p>
20
20
  **Important:** Each tunnel in an IPSec connection can use either static routing or BGP dynamic
21
21
  * routing (see the {@link IPSecConnectionTunnel} object's
22
- * `routing` attribute). Originally only static routing was supported and
22
+ * {@code routing} attribute). Originally only static routing was supported and
23
23
  * every IPSec connection was required to have at least one static route configured.
24
24
  * To maintain backward compatibility in the API when support for BPG dynamic routing was introduced,
25
25
  * the API accepts an empty list of static routes if you configure both of the IPSec tunnels to use
26
- * BGP dynamic routing. If you switch a tunnel's routing from `BGP` to `STATIC`, you must first
26
+ * BGP dynamic routing. If you switch a tunnel's routing from {@code BGP} to {@code STATIC}, you must first
27
27
  * ensure that the IPSec connection is configured with at least one valid CIDR block static route.
28
28
  * Oracle uses the IPSec connection's static routes when routing a tunnel's traffic *only*
29
- * if that tunnel's `routing` attribute = `STATIC`. Otherwise the static routes are ignored.
29
+ * if that tunnel's {@code routing} attribute = {@code STATIC}. Otherwise the static routes are ignored.
30
30
  * <p>
31
31
  For more information about the workflow for setting up an IPSec connection, see
32
32
  * [Site-to-Site VPN Overview](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/overviewIPsec.htm).
@@ -47,7 +47,7 @@ export interface IPSecConnection {
47
47
  "cpeId": string;
48
48
  /**
49
49
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
50
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
50
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
51
51
  *
52
52
  */
53
53
  "definedTags"?: {
@@ -67,7 +67,7 @@ export interface IPSecConnection {
67
67
  "drgId": string;
68
68
  /**
69
69
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
70
- * Example: `{\"bar-key\": \"value\"}`
70
+ * Example: {@code {\"bar-key\": \"value\"}}
71
71
  *
72
72
  */
73
73
  "freeformTags"?: {
@@ -84,23 +84,23 @@ export interface IPSecConnection {
84
84
  /**
85
85
  * Your identifier for your CPE device. Can be either an IP address or a hostname (specifically,
86
86
  * the fully qualified domain name (FQDN)). The type of identifier here must correspond
87
- * to the value for `cpeLocalIdentifierType`.
87
+ * to the value for {@code cpeLocalIdentifierType}.
88
88
  * <p>
89
- If you don't provide a value when creating the IPSec connection, the `ipAddress` attribute
90
- * for the {@link Cpe} object specified by `cpeId` is used as the `cpeLocalIdentifier`.
89
+ If you don't provide a value when creating the IPSec connection, the {@code ipAddress} attribute
90
+ * for the {@link Cpe} object specified by {@code cpeId} is used as the {@code cpeLocalIdentifier}.
91
91
  * <p>
92
92
  For information about why you'd provide this value, see
93
93
  * [If Your CPE Is Behind a NAT Device](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/overviewIPsec.htm#nat).
94
94
  * <p>
95
- Example IP address: `10.0.3.3`
95
+ Example IP address: {@code 10.0.3.3}
96
96
  * <p>
97
- Example hostname: `cpe.example.com`
97
+ Example hostname: {@code cpe.example.com}
98
98
  *
99
99
  */
100
100
  "cpeLocalIdentifier"?: string;
101
101
  /**
102
102
  * The type of identifier for your CPE device. The value here must correspond to the value
103
- * for `cpeLocalIdentifier`.
103
+ * for {@code cpeLocalIdentifier}.
104
104
  *
105
105
  */
106
106
  "cpeLocalIdentifierType"?: IPSecConnection.CpeLocalIdentifierType;
@@ -116,16 +116,16 @@ export interface IPSecConnection {
116
116
  The CIDR can be either IPv4 or IPv6. IPv6 addressing is supported for all commercial and government regions.
117
117
  * See [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
118
118
  * <p>
119
- Example: `10.0.1.0/24`
119
+ Example: {@code 10.0.1.0/24}
120
120
  * <p>
121
- Example: `2001:db8::/32`
121
+ Example: {@code 2001:db8::/32}
122
122
  *
123
123
  */
124
124
  "staticRoutes": Array<string>;
125
125
  /**
126
126
  * The date and time the IPSec connection was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
127
127
  * <p>
128
- Example: `2016-08-25T21:10:29.600Z`
128
+ Example: {@code 2016-08-25T21:10:29.600Z}
129
129
  *
130
130
  */
131
131
  "timeCreated"?: Date;
@@ -14,7 +14,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
14
14
  */
15
15
  import * as model from "../model";
16
16
  /**
17
- * Defines the `ProtocolParameters` configuration for the [ICMP](https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml) protocol.
17
+ * Defines the {@code ProtocolParameters} configuration for the [ICMP](https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml) protocol.
18
18
  *
19
19
  */
20
20
  export interface IcmpTrafficProtocolParameters extends model.TrafficProtocolParameters {
@@ -28,7 +28,7 @@ export interface IngressSecurityRule {
28
28
  */
29
29
  "isStateless"?: boolean;
30
30
  /**
31
- * The transport protocol. Specify either `all` or an IPv4 protocol number as
31
+ * The transport protocol. Specify either {@code all} or an IPv4 protocol number as
32
32
  * defined in
33
33
  * [Protocol Numbers](http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml).
34
34
  * Options are supported only for ICMP (\"1\"), TCP (\"6\"), UDP (\"17\"), and ICMPv6 (\"58\").
@@ -41,24 +41,24 @@ export interface IngressSecurityRule {
41
41
  * <p>
42
42
  Allowed values:
43
43
  * <p>
44
- * IP address range in CIDR notation. For example: `192.168.1.0/24` or `2001:0db8:0123:45::/56`.
44
+ * IP address range in CIDR notation. For example: {@code 192.168.1.0/24} or {@code 2001:0db8:0123:45::/56}.
45
45
  * IPv6 addressing is supported for all commercial and government regions. See
46
46
  * [IPv6 Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/ipv6.htm).
47
47
  * <p>
48
- * The `cidrBlock` value for a {@link Service}, if you're
49
- * setting up a security list rule for traffic coming from a particular `Service` through
50
- * a service gateway. For example: `oci-phx-objectstorage`.
48
+ * The {@code cidrBlock} value for a {@link Service}, if you're
49
+ * setting up a security list rule for traffic coming from a particular {@code Service} through
50
+ * a service gateway. For example: {@code oci-phx-objectstorage}.
51
51
  *
52
52
  */
53
53
  "source": string;
54
54
  /**
55
- * Type of source for the rule. The default is `CIDR_BLOCK`.
55
+ * Type of source for the rule. The default is {@code CIDR_BLOCK}.
56
56
  * <p>
57
- * `CIDR_BLOCK`: If the rule's `source` is an IP address range in CIDR notation.
57
+ * {@code CIDR_BLOCK}: If the rule's {@code source} is an IP address range in CIDR notation.
58
58
  * <p>
59
- * `SERVICE_CIDR_BLOCK`: If the rule's `source` is the `cidrBlock` value for a
59
+ * {@code SERVICE_CIDR_BLOCK}: If the rule's {@code source} is the {@code cidrBlock} value for a
60
60
  * {@link Service} (the rule is for traffic coming from a
61
- * particular `Service` through a service gateway).
61
+ * particular {@code Service} through a service gateway).
62
62
  *
63
63
  */
64
64
  "sourceType"?: IngressSecurityRule.SourceType;
@@ -29,7 +29,7 @@ export interface InternetGateway {
29
29
  "compartmentId": string;
30
30
  /**
31
31
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
32
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
32
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
33
33
  *
34
34
  */
35
35
  "definedTags"?: {
@@ -45,7 +45,7 @@ export interface InternetGateway {
45
45
  "displayName"?: string;
46
46
  /**
47
47
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
48
- * Example: `{\"bar-key\": \"value\"}`
48
+ * Example: {@code {\"bar-key\": \"value\"}}
49
49
  *
50
50
  */
51
51
  "freeformTags"?: {
@@ -68,7 +68,7 @@ export interface InternetGateway {
68
68
  /**
69
69
  * The date and time the internet gateway was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
70
70
  * <p>
71
- Example: `2016-08-25T21:10:29.600Z`
71
+ Example: {@code 2016-08-25T21:10:29.600Z}
72
72
  *
73
73
  */
74
74
  "timeCreated"?: Date;
@@ -14,12 +14,12 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
14
14
  */
15
15
  import * as model from "../model";
16
16
  /**
17
- * Defines the details required for an IP_ADDRESS-type `Endpoint`.
17
+ * Defines the details required for an IP_ADDRESS-type {@code Endpoint}.
18
18
  *
19
19
  */
20
20
  export interface IpAddressEndpoint extends model.Endpoint {
21
21
  /**
22
- * The IPv4 address of the `Endpoint`.
22
+ * The IPv4 address of the {@code Endpoint}.
23
23
  *
24
24
  */
25
25
  "address": string;
@@ -14,7 +14,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
14
14
  */
15
15
  /**
16
16
  * An *IPv6* is a conceptual term that refers to an IPv6 address and related properties.
17
- * The `IPv6` object is the API representation of an IPv6.
17
+ * The {@code IPv6} object is the API representation of an IPv6.
18
18
  * <p>
19
19
  You can create and assign an IPv6 to any VNIC that is in an IPv6-enabled subnet in an
20
20
  * IPv6-enabled VCN.
@@ -32,7 +32,7 @@ export interface Ipv6 {
32
32
  "compartmentId": string;
33
33
  /**
34
34
  * Defined tags for this resource. Each key is predefined and scoped to a namespace.
35
- * Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
35
+ * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}}
36
36
  *
37
37
  */
38
38
  "definedTags"?: {
@@ -48,7 +48,7 @@ export interface Ipv6 {
48
48
  "displayName": string;
49
49
  /**
50
50
  * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only.
51
- * Example: `{\"bar-key\": \"value\"}`
51
+ * Example: {@code {\"bar-key\": \"value\"}}
52
52
  *
53
53
  */
54
54
  "freeformTags"?: {
@@ -59,10 +59,10 @@ export interface Ipv6 {
59
59
  */
60
60
  "id": string;
61
61
  /**
62
- * The IPv6 address of the `IPv6` object. The address is within the IPv6 CIDR block of the VNIC's subnet
63
- * (see the `ipv6CidrBlock` attribute for the {@link Subnet} object.
62
+ * The IPv6 address of the {@code IPv6} object. The address is within the IPv6 CIDR block of the VNIC's subnet
63
+ * (see the {@code ipv6CidrBlock} attribute for the {@link Subnet} object.
64
64
  * <p>
65
- Example: `2001:0db8:0123:1111:abcd:ef01:2345:6789`
65
+ Example: {@code 2001:0db8:0123:1111:abcd:ef01:2345:6789}
66
66
  *
67
67
  */
68
68
  "ipAddress": string;
@@ -77,7 +77,7 @@ export interface Ipv6 {
77
77
  /**
78
78
  * The date and time the IPv6 was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
79
79
  * <p>
80
- Example: `2016-08-25T21:10:29.600Z`
80
+ Example: {@code 2016-08-25T21:10:29.600Z}
81
81
  *
82
82
  */
83
83
  "timeCreated": Date;
@@ -46,7 +46,7 @@ export interface LetterOfAuthority {
46
46
  /**
47
47
  * The date and time the Letter of Authority was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339).
48
48
  * <p>
49
- Example: `2016-08-25T21:10:29.600Z`
49
+ Example: {@code 2016-08-25T21:10:29.600Z}
50
50
  *
51
51
  */
52
52
  "timeIssued"?: Date;
@@ -14,7 +14,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
14
14
  */
15
15
  import * as model from "../model";
16
16
  /**
17
- * Defines the details required for a LOAD_BALANCER-type `Endpoint`.
17
+ * Defines the details required for a LOAD_BALANCER-type {@code Endpoint}.
18
18
  *
19
19
  */
20
20
  export interface LoadBalancerEndpoint extends model.Endpoint {
@@ -14,7 +14,7 @@ documentation for the [Network Path Analyzer](/iaas/Content/Network/Concepts/pat
14
14
  */
15
15
  import * as model from "../model";
16
16
  /**
17
- * Defines the details required for a LOAD_BALANCER_LISTENER-type `Endpoint`.
17
+ * Defines the details required for a LOAD_BALANCER_LISTENER-type {@code Endpoint}.
18
18
  *
19
19
  */
20
20
  export interface LoadBalancerListenerEndpoint extends model.Endpoint {