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: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ type ConfigurationProvider interface {
55
55
}
56
56
```
57
57
58
-
### Making a request
58
+
### Making a Request
59
59
To make a request to an Oracle Cloud Infrastructure service, create a client for the service and then use the client to call a function from the service.
60
60
61
61
-*Creating a client*: All packages provide a function to create clients, using the naming convention `New<ServiceName>ClientWithConfigurationProvider`,
@@ -132,8 +132,8 @@ See [CHANGELOG](/CHANGELOG.md).
132
132
## Known Issues
133
133
You can find information on any known issues with the SDK here and under the [Issues](https://github.com/oracle/oci-go-sdk/issues) tab of this project's GitHub repository.
134
134
135
-
## Building and testing
136
-
### Dev dependencies
135
+
## Building and Testing
136
+
### Dev Dependencies
137
137
- Install [Testify](https://github.com/stretchr/testify) with the command:
// The common pattern (or lack thereof) to which the steering policy adheres. This
30
-
// value restricts the possible configurations of rules, but thereby supports
31
-
// specifically tailored interfaces. Values other than "CUSTOM" require the rules to
32
-
// begin with an unconditional FILTER that keeps answers contingent upon
33
-
// `answer.isDisabled != true`, followed
34
-
// _if and only if the policy references a health check monitor_ by an unconditional
35
-
// HEALTH rule, and require the last rule to be an unconditional LIMIT.
36
-
// What must precede the LIMIT rule is determined by the template value:
37
-
// - FAILOVER requires exactly an unconditional PRIORITY rule that ranks answers by pool.
38
-
// Each answer pool must have a unique priority value assigned to it. Answer data must
39
-
// be defined in the `defaultAnswerData` property for the rule and the `cases` property
40
-
// must not be defined.
41
-
// - LOAD_BALANCE requires exactly an unconditional WEIGHTED rule that shuffles answers
42
-
// by name. Answer data must be defined in the `defaultAnswerData` property for the
43
-
// rule and the `cases` property must not be defined.
44
-
// - ROUTE_BY_GEO requires exactly one PRIORITY rule that ranks answers by pool using the
45
-
// geographical location of the client as a condition. Within that rule you may only
46
-
// use `query.client.geoKey` in the `caseCondition` expressions for defining the cases.
47
-
// For each case in the PRIORITY rule each answer pool must have a unique priority
48
-
// value assigned to it. Answer data can only be defined within cases and
49
-
// `defaultAnswerData` cannot be used in the PRIORITY rule.
50
-
// - ROUTE_BY_ASN requires exactly one PRIORITY rule that ranks answers by pool using the
51
-
// ASN of the client as a condition. Within that rule you may only use
52
-
// `query.client.asn` in the `caseCondition` expressions for defining the cases.
53
-
// For each case in the PRIORITY rule each answer pool must have a unique priority
54
-
// value assigned to it. Answer data can only be defined within cases and
55
-
// `defaultAnswerData` cannot be used in the PRIORITY rule.
56
-
// - ROUTE_BY_IP requires exactly one PRIORITY rule that ranks answers by pool using the
57
-
// IP subnet of the client as a condition. Within that rule you may only use
58
-
// `query.client.address` in the `caseCondition` expressions for defining the cases.
59
-
// For each case in the PRIORITY rule each answer pool must have a unique priority
60
-
// value assigned to it. Answer data can only be defined within cases and
61
-
// `defaultAnswerData` cannot be used in the PRIORITY rule.
62
-
// - CUSTOM allows an arbitrary configuration of rules.
63
-
// For an existing steering policy, the template value may be changed to any of the
64
-
// supported options but the resulting policy must conform to the requirements for the
65
-
// new template type or else a Bad Request error will be returned.
28
+
// A set of predefined rules based on the desired purpose of the steering policy. Each
29
+
// template utilizes Traffic Management's rules in a different order to produce the desired
30
+
// results when answering DNS queries.
31
+
//
32
+
// **Example:** The `FAILOVER` template determines answers by filtering the policy's answers
33
+
// using the `FILTER` rule first, then the following rules in succession: `HEALTH`, `PRIORITY`,
34
+
// and `LIMIT`. This gives the domain dynamic failover capability.
35
+
//
36
+
// It is **strongly recommended** to use a template other than `CUSTOM` when creating
37
+
// a steering policy.
38
+
//
39
+
// All templates require the rule order to begin with an unconditional `FILTER` rule that keeps
40
+
// answers contingent upon `answer.isDisabled != true`, except for `CUSTOM`. A defined
41
+
// `HEALTH` rule must follow the `FILTER` rule if the policy references a `healthCheckMonitorId`.
42
+
// The last rule of a template must must be a `LIMIT` rule. For more information about templates
43
+
// and code examples, see Traffic Management API Guide (https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).
44
+
// **Template Types**
45
+
// * `FAILOVER` - Uses health check information on your endpoints to determine which DNS answers
46
+
// to serve. If an endpoint fails a health check, the answer for that endpoint will be removed
47
+
// from the list of available answers until the endpoint is detected as healthy.
48
+
//
49
+
// * `LOAD_BALANCE` - Distributes web traffic to specified endpoints based on defined weights.
50
+
//
51
+
// * `ROUTE_BY_GEO` - Answers DNS queries based on the query's geographic location. For a list of geographic
52
+
// locations to route by, see Traffic Management Geographic Locations (https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Reference/trafficmanagementgeo.htm).
53
+
//
54
+
// * `ROUTE_BY_ASN` - Answers DNS queries based on the query's originating ASN.
55
+
//
56
+
// * `ROUTE_BY_IP` - Answers DNS queries based on the query's IP address.
57
+
//
58
+
// * `CUSTOM` - Allows a customized configuration of rules.
// CreateSteeringPolicy Creates a new steering policy in the specified compartment.
62
+
// CreateSteeringPolicy Creates a new steering policy in the specified compartment. For more information on
63
+
// creating policies with templates, see Traffic Management API Guide (https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).
// PatchDomainRecords Updates records in the specified zone at a domain. You can update one record or all records for the specified zone depending on the changes provided in the request body. You can also add or remove records using this function.
805
+
// PatchDomainRecords Updates records in the specified zone at a domain. You can update
806
+
// one record or all records for the specified zone depending on the changes
807
+
// provided in the request body. You can also add or remove records using this
0 commit comments