You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/core/dhcp_options.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,19 @@ Note that the `options` object you provide replaces the entire existing set of o
77
77
The following arguments support updates:
78
78
*`display_name` - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
79
79
*`options` - A set of [DHCP Options](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/20160918/DhcpDnsOption/)
80
-
80
+
*`type` - The specific DHCP option. Either `DomainNameServer` (for [DhcpDnsOption](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/20160918/DhcpDnsOption/)) or `SearchDomain` (for [DhcpSearchDomainOption](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/20160918/DhcpSearchDomainOption/)).
81
+
* `custom_dns_servers` - Used only when `type` is `DomainNameServer`. If you set `server_type` to `CustomDnsServer`, specify the IP address of at least one DNS server of your choice (three maximum).
82
+
* `server_type` - Used only when `type` is `DomainNameServer`. It can be set to one of the following values:
83
+
* `VcnLocal`: Reserved for future use.
84
+
* `VcnLocalPlusInternet`: Also referred to as "Internet and VCN Resolver". Instances can resolve internet hostnames (no Internet Gateway is required), and can resolve hostnames of instances in the VCN. This is the default value in the default set of DHCP options in the VCN. For the Internet and VCN Resolver to work across the VCN, there must also be a DNS label set for the VCN, a DNS label set for each subnet, and a hostname for each instance. The Internet and VCN Resolver also enables reverse DNS lookup, which lets you determine the hostname corresponding to the private IP address.
85
+
* `CustomDnsServer`: Instances use a DNS server of your choice (three maximum).
86
+
* `search_domain_names` - Used only when `type` is `SearchDomainNames`. A single search domain name according to [RFC 952](https://tools.ietf.org/html/rfc952) and [RFC 1123](https://tools.ietf.org/html/rfc1123). During a DNS query,
87
+
the OS will append this search domain name to the value being queried.
88
+
If you set [DhcpDnsOption](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/iaas/20160918/DhcpDnsOption/) to `VcnLocalPlusInternet`,
89
+
and you assign a DNS label to the VCN during creation, the search domain name in the
90
+
VCN's default set of DHCP options is automatically set to the VCN domain (for example, `vcn1.oraclevcn.com`).
91
+
If you don't want to use a search domain name, omit this option from the set of DHCP options. Do not include this option with an empty list
92
+
of search domain names, or with an empty string as the value for any search domain name.
81
93
82
94
** IMPORTANT **
83
95
Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
Copy file name to clipboardExpand all lines: docs/core/route_tables.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,6 +58,8 @@ Note that the `routeRules` object you provide replaces the entire existing set o
58
58
The following arguments support updates:
59
59
*`display_name` - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
60
60
*`route_rules` - The collection of rules used for routing destination IPs to network devices.
61
+
* `cidr_block` - A destination IP address range in CIDR notation. Matching packets will be routed to the indicated network entity (the target). Example: `0.0.0.0/0`
62
+
* `network_entity_id` - The OCID for the route rule's target. For information about the type of targets you can specify, see [Route Tables](https://docs.us-phoenix-1.oraclecloud.com/Content/Network/Tasks/managingroutetables.htm).
Copy file name to clipboardExpand all lines: docs/load_balancer/backend_sets.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# oci_load_balancer_backend_set
1
+
# oci_load_balancer_backendset
2
2
3
3
## BackendSet Resource
4
4
@@ -65,20 +65,21 @@ The following arguments are supported:
65
65
Updates a backend set.
66
66
67
67
The following arguments support updates:
68
-
* `backup` - Whether the load balancer should treat this server as a backup unit. If `true`, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy. Example: `true`
69
-
* `drain` - Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: `true`
70
-
* `offline` - Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: `true`
71
-
* `weight` - The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see [How Load Balancing Policies Work](https://docs.us-phoenix-1.oraclecloud.com/Content/Balance/Reference/lbpolicies.htm). Example: `3`
68
+
*`health_checker` -
72
69
* `interval_ms` - The interval between health checks, in milliseconds. Example: `30000`
73
70
* `port` - The backend server port against which to run the health check. If the port is not specified, the load balancer uses the port information from the `Backend` object. Example: `8080`
71
+
* `protocol` - The protocol the health check must use; either HTTP or TCP. Example: `HTTP`
74
72
* `response_body_regex` - A regular expression for parsing the response body from the backend server. Example: `^(500|40[1348])$`
75
73
* `retries` - The number of retries to attempt before a backend server is considered "unhealthy". Example: `3`
76
74
* `return_code` - The status code a healthy backend server should return. Example: `200`
77
75
* `timeout_in_millis` - The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. Example: `6000`
78
76
* `url_path` - The path against which to run the health check. Example: `/healthcheck`
77
+
*`policy` - The load balancer policy for the backend set. To get a list of available policies, use the [ListPolicies](https://docs.us-phoenix-1.oraclecloud.com/api/#/en/loadbalancer/20170115/LoadBalancerPolicy/ListPolicies) operation. Example: `LEAST_CONNECTIONS`
79
78
*`session_persistence_configuration` -
79
+
* `cookie_name` - The name of the cookie used to detect a session initiated by the backend server. Use '*' to specify that any cookie set by the backend causes the session to persist. Example: `myCookieName`
80
80
* `disable_fallback` - Whether the load balancer is prevented from directing traffic from a persistent session client to a different backend server if the original server is unavailable. Defaults to false. Example: `true`
81
81
*`ssl_configuration` -
82
+
* `certificate_name` - A friendly name for the certificate bundle. It must be unique and it cannot be changed. Valid certificate bundle names include only alphanumeric characters, dashes, and underscores. Certificate bundle names cannot contain spaces. Avoid entering confidential information. Example: `My_certificate_bundle`
82
83
* `verify_depth` - The maximum depth for peer certificate chain verification. Example: `3`
83
84
* `verify_peer_certificate` - Whether the load balancer listener should verify peer certificates. Example: `true`
84
85
@@ -89,7 +90,7 @@ Any change to a property that does not support update will force the destruction
Copy file name to clipboardExpand all lines: docs/load_balancer/backends.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,11 @@ The following arguments are supported:
36
36
Updates the configuration of a backend server within the specified backend set.
37
37
38
38
The following arguments support updates:
39
-
* NO arguments in this resource support updates
39
+
*`backup` - Whether the load balancer should treat this server as a backup unit. If `true`, the load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "backup" fail the health check policy. Example: `true`
40
+
*`drain` - Whether the load balancer should drain this server. Servers marked "drain" receive no new incoming traffic. Example: `true`
41
+
*`offline` - Whether the load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: `true`
42
+
*`weight` - The load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives 3 times the number of new connections as a server weighted '1'. For more information on load balancing policies, see [How Load Balancing Policies Work](https://docs.us-phoenix-1.oraclecloud.com/Content/Balance/Reference/lbpolicies.htm). Example: `3`
43
+
40
44
41
45
** IMPORTANT **
42
46
Any change to a property that does not support update will force the destruction and recreation of the resource with the new property values
0 commit comments