oci 2.5.3 → 2.5.4

data/lib/oci/dns/models/steering_policy_answer.rb

@@ -6,34 +6,81 @@ require 'date'
 module OCI
   # DNS record data with metadata for processing in a steering policy.
   #
-  # *Warning:* Oracle recommends that you avoid using any confidential information when you supply string values using the API.
+  #
+  # **Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
   #
   class Dns::Models::SteeringPolicyAnswer # rubocop:disable Metrics/LineLength
     # **[Required]** A user-friendly name for the answer, unique within the steering policy.
+    # An answer's `name` property can be referenced in `answerCondition` properties
+    # of rules using `answer.name`.
+    #
+    # **Example:**
+    #
+    #   \"rules\": [
+    #     {
+    #       \"ruleType\": \"FILTER\",
+    #       \"defaultAnswerData\":  [
+    #         {
+    #           \"answerCondition\": \"answer.name == 'server 1'\",
+    #           \"shouldKeep\": true
+    #         }
+    #       ]
+    #     }
+    #   ]
+    #
     # @return [String]
     attr_accessor :name
 
     # **[Required]** The canonical name for the record's type. Only A, AAAA, and CNAME are supported. For more
-    # information, see [Resource Record (RR) TYPEs](https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml#dns-parameters-4).
+    # information, see [Supported DNS Resource Record Types](https://docs.cloud.oracle.com/iaas/Content/DNS/Reference/supporteddnsresource.htm).
     #
     # @return [String]
     attr_accessor :rtype
 
     # **[Required]** The record's data, as whitespace-delimited tokens in
-    # type-specific presentation format.
+    # type-specific presentation format. All RDATA is normalized and the
+    # returned presentation of your RDATA may differ from its initial input.
+    # For more information about RDATA, see [Supported DNS Resource Record Types](https://docs.cloud.oracle.com/iaas/Content/DNS/Reference/supporteddnsresource.htm).
     #
     # @return [String]
     attr_accessor :rdata
 
-    # The freeform name of a group of one or more records (e.g., a data center or a geographic
-    # region) in which this one is included.
+    # The freeform name of a group of one or more records in which this record is included,
+    # such as \"LAX data center\". An answer's `pool` property can be referenced in `answerCondition`
+    # properties of rules using `answer.pool`.
+    #
+    # **Example:**
+    #
+    #   \"rules\": [
+    #     {
+    #       \"ruleType\": \"FILTER\",
+    #       \"defaultAnswerData\":  [
+    #         {
+    #           \"answerCondition\": \"answer.pool == 'US East Servers'\",
+    #           \"shouldKeep\": true
+    #         }
+    #       ]
+    #     }
+    #   ]
     #
     # @return [String]
     attr_accessor :pool
 
-    # Whether or not an answer should be excluded from responses, e.g. because the corresponding
-    # server is down for maintenance. Note, however, that such filtering is not automatic and
-    # will only take place if a rule implements it.
+    # Set this property to `true` to indicate that the answer is administratively disabled,
+    # such as when the corresponding server is down for maintenance. An answer's `isDisabled`
+    # property can be referenced in `answerCondition` properties in rules using `answer.isDisabled`.
+    #
+    # **Example:**
+    #   \"rules\": [
+    #     {
+    #       \"ruleType\": \"FILTER\",
+    #       \"defaultAnswerData\": [
+    #         {
+    #           \"answerCondition\": \"answer.isDisabled != true\",
+    #           \"shouldKeep\": true
+    #         }
+    #       ]
+    #     },
     #
     # @return [BOOLEAN]
     attr_accessor :is_disabled

data/lib/oci/dns/models/steering_policy_attachment.rb

@@ -5,10 +5,12 @@ require 'logger'
 
 # rubocop:disable Lint/UnneededCopDisableDirective
 module OCI
-  # An attachment between a steering policy and a domain.
-  # An attachment occludes all records at its domain that are of a covered rtype, constructing
-  # DNS responses from its steering policy rather than from those domain records.
-  # A domain can have at most one attachment covering any given rtype.
+  # An attachment between a steering policy and a domain. An attachment constructs
+  # DNS responses using its steering policy instead of the records at its defined domain.
+  # Only records of the policy's covered rtype are blocked at the domain.
+  # A domain can have a maximum of one attachment covering any given rtype.
+  #
+  # **Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
   #
   class Dns::Models::SteeringPolicyAttachment # rubocop:disable Metrics/LineLength
     LIFECYCLE_STATE_ENUM = [
@@ -31,7 +33,7 @@ module OCI
     attr_accessor :domain_name
 
     # A user-friendly name for the steering policy attachment.
-    # Does not have to be unique, and it's changeable.
+    # Does not have to be unique and can be changed.
     # Avoid entering confidential information.
     #
     # @return [String]
@@ -56,8 +58,7 @@ module OCI
     # @return [String]
     attr_accessor :id
 
-    # The date and time the resource was created in \"YYYY-MM-ddThh:mmZ\" format
-    # with a Z offset, as defined by RFC 3339.
+    # The date and time the resource was created, expressed in RFC 3339 timestamp format.
     #
     # **Example:** `2016-07-22T17:23:59:60Z`
     #

data/lib/oci/dns/models/steering_policy_attachment_summary.rb

@@ -27,7 +27,7 @@ module OCI
     attr_accessor :domain_name
 
     # A user-friendly name for the steering policy attachment.
-    # Does not have to be unique, and it's changeable.
+    # Does not have to be unique and can be changed.
     # Avoid entering confidential information.
     #
     # @return [String]
@@ -52,8 +52,7 @@ module OCI
     # @return [String]
     attr_accessor :id
 
-    # The date and time the resource was created in \"YYYY-MM-ddThh:mmZ\" format
-    # with a Z offset, as defined by RFC 3339.
+    # The date and time the resource was created, expressed in RFC 3339 timestamp format.
     #
     # **Example:** `2016-07-22T17:23:59:60Z`
     #

data/lib/oci/dns/models/steering_policy_filter_answer_data.rb

@@ -6,10 +6,12 @@ require 'date'
 module OCI
   # SteeringPolicyFilterAnswerData model.
   class Dns::Models::SteeringPolicyFilterAnswerData # rubocop:disable Metrics/LineLength
+    # An expression that is used to select a set of answers that match a condition. For example, answers with matching pool properties.
+    #
     # @return [String]
     attr_accessor :answer_condition
 
-    # Keep the answer if the value is `true`.
+    # Keeps the answer only if the value is `true`.
     # @return [BOOLEAN]
     attr_accessor :should_keep
 

data/lib/oci/dns/models/steering_policy_filter_rule.rb

@@ -7,13 +7,22 @@ require_relative 'steering_policy_rule'
 module OCI
   # SteeringPolicyFilterRule model.
   class Dns::Models::SteeringPolicyFilterRule < Dns::Models::SteeringPolicyRule # rubocop:disable Metrics/LineLength
+    # An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+    # configurations for how it should behave during processing for any given DNS query. When a rule has
+    # no sequence of `cases`, it is always evaluated with the same configuration during processing. When
+    # a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
+    # non-empty sequence of `cases`, its behavior during processing is configured by the first matching
+    # `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+    # `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+    # evaluates to true for the given query.
+    #
     # @return [Array<OCI::Dns::Models::SteeringPolicyFilterRuleCase>]
     attr_accessor :cases
 
     # Defines a default set of answer conditions and values that are applied to an answer when
-    # `cases` is not defined for the rule or a matching case does not have any matching
-    # `answerCondition`s in its `answerData`. `defaultAnswerData` is **not** applied if `cases` is
-    # defined and there are no matching cases.
+    # `cases` is not defined for the rule, or a matching case does not have any matching
+    # `answerCondition`s in its `answerData`. `defaultAnswerData` is not applied if `cases` is
+    # defined and there are no matching cases. In this scenario, the next rule will be processed.
     #
     # @return [Array<OCI::Dns::Models::SteeringPolicyFilterAnswerData>]
     attr_accessor :default_answer_data

data/lib/oci/dns/models/steering_policy_filter_rule_case.rb

@@ -6,9 +6,17 @@ require 'date'
 module OCI
   # SteeringPolicyFilterRuleCase model.
   class Dns::Models::SteeringPolicyFilterRuleCase # rubocop:disable Metrics/LineLength
+    # An expression that uses conditions at the time of a DNS query to indicate
+    # whether a case matches. Conditions may include the geographical location, IP
+    # subnet, or ASN the DNS query originated. **Example:** If you have an
+    # office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
+    # expression `query.client.subnet in ('192.0.2.0/24')` to define a case that
+    # matches queries from that office.
+    #
     # @return [String]
     attr_accessor :case_condition
 
+    # An array of `SteeringPolicyFilterAnswerData` objects.
     # @return [Array<OCI::Dns::Models::SteeringPolicyFilterAnswerData>]
     attr_accessor :answer_data
 

data/lib/oci/dns/models/steering_policy_health_rule.rb

@@ -7,6 +7,15 @@ require_relative 'steering_policy_rule'
 module OCI
   # SteeringPolicyHealthRule model.
   class Dns::Models::SteeringPolicyHealthRule < Dns::Models::SteeringPolicyRule # rubocop:disable Metrics/LineLength
+    # An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+    # configurations for how it should behave during processing for any given DNS query. When a rule has
+    # no sequence of `cases`, it is always evaluated with the same configuration during processing. When
+    # a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
+    # non-empty sequence of `cases`, its behavior during processing is configured by the first matching
+    # `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+    # `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+    # evaluates to true for the given query.
+    #
     # @return [Array<OCI::Dns::Models::SteeringPolicyHealthRuleCase>]
     attr_accessor :cases
 

data/lib/oci/dns/models/steering_policy_health_rule_case.rb

@@ -6,6 +6,13 @@ require 'date'
 module OCI
   # SteeringPolicyHealthRuleCase model.
   class Dns::Models::SteeringPolicyHealthRuleCase # rubocop:disable Metrics/LineLength
+    # An expression that uses conditions at the time of a DNS query to indicate
+    # whether a case matches. Conditions may include the geographical location, IP
+    # subnet, or ASN the DNS query originated. **Example:** If you have an
+    # office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
+    # expression `query.client.subnet in ('192.0.2.0/24')` to define a case that
+    # matches queries from that office.
+    #
     # @return [String]
     attr_accessor :case_condition
 

data/lib/oci/dns/models/steering_policy_limit_rule.rb

@@ -7,12 +7,22 @@ require_relative 'steering_policy_rule'
 module OCI
   # SteeringPolicyLimitRule model.
   class Dns::Models::SteeringPolicyLimitRule < Dns::Models::SteeringPolicyRule # rubocop:disable Metrics/LineLength
+    # An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+    # configurations for how it should behave during processing for any given DNS query. When a rule has
+    # no sequence of `cases`, it is always evaluated with the same configuration during processing. When
+    # a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
+    # non-empty sequence of `cases`, its behavior during processing is configured by the first matching
+    # `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+    # `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+    # evaluates to true for the given query.
+    #
     # @return [Array<OCI::Dns::Models::SteeringPolicyLimitRuleCase>]
     attr_accessor :cases
 
     # Defines a default count if `cases` is not defined for the rule or a matching case does
     # not define `count`. `defaultCount` is **not** applied if `cases` is defined and there
-    # are no matching cases.
+    # are no matching cases. In this scenario, the next rule will be processed. If no rules
+    # remain to be processed, the answer will be chosen from the remaining list of answers.
     #
     # @return [Integer]
     attr_accessor :default_count

data/lib/oci/dns/models/steering_policy_limit_rule_case.rb

@@ -6,10 +6,21 @@ require 'date'
 module OCI
   # SteeringPolicyLimitRuleCase model.
   class Dns::Models::SteeringPolicyLimitRuleCase # rubocop:disable Metrics/LineLength
+    # An expression that uses conditions at the time of a DNS query to indicate
+    # whether a case matches. Conditions may include the geographical location, IP
+    # subnet, or ASN the DNS query originated. **Example:** If you have an
+    # office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
+    # expression `query.client.subnet in ('192.0.2.0/24')` to define a case that
+    # matches queries from that office.
+    #
     # @return [String]
     attr_accessor :case_condition
 
-    # This attribute is required.
+    # **[Required]** The number of answers allowed to remain after the limit rule has been processed, keeping only the
+    # first of the remaining answers in the list. Example: If the `count` property is set to `2` and
+    # four answers remain before the limit rule is processed, only the first two answers in the list will
+    # remain after the limit rule has been processed.
+    #
     # @return [Integer]
     attr_accessor :count
 

data/lib/oci/dns/models/steering_policy_priority_answer_data.rb

@@ -6,9 +6,15 @@ require 'date'
 module OCI
   # SteeringPolicyPriorityAnswerData model.
   class Dns::Models::SteeringPolicyPriorityAnswerData # rubocop:disable Metrics/LineLength
+    # An expression that is used to select a set of answers that match a condition. For example, answers with matching pool properties.
+    #
     # @return [String]
     attr_accessor :answer_condition
 
+    # **[Required]** The rank assigned to the set of answers that match the expression in `answerCondition`.
+    # Answers with the lowest values move to the beginning of the list without changing the
+    # relative order of those with the same value. Answers can be given a value between `0` and `255`.
+    #
     # @return [Integer]
     attr_accessor :value
 

data/lib/oci/dns/models/steering_policy_priority_rule.rb

@@ -7,13 +7,22 @@ require_relative 'steering_policy_rule'
 module OCI
   # SteeringPolicyPriorityRule model.
   class Dns::Models::SteeringPolicyPriorityRule < Dns::Models::SteeringPolicyRule # rubocop:disable Metrics/LineLength
+    # An array of `caseConditions`. A rule may optionally include a sequence of cases defining alternate
+    # configurations for how it should behave during processing for any given DNS query. When a rule has
+    # no sequence of `cases`, it is always evaluated with the same configuration during processing. When
+    # a rule has an empty sequence of `cases`, it is always ignored during processing. When a rule has a
+    # non-empty sequence of `cases`, its behavior during processing is configured by the first matching
+    # `case` in the sequence. When a rule has no matching cases the rule is ignored. A rule case with no
+    # `caseCondition` always matches. A rule case with a `caseCondition` matches only when that expression
+    # evaluates to true for the given query.
+    #
     # @return [Array<OCI::Dns::Models::SteeringPolicyPriorityRuleCase>]
     attr_accessor :cases
 
     # Defines a default set of answer conditions and values that are applied to an answer when
     # `cases` is not defined for the rule or a matching case does not have any matching
-    # `answerCondition`s in its `answerData`. `defaultAnswerData` is **not** applied if `cases` is
-    # defined and there are no matching cases.
+    # `answerCondition`s in its `answerData`. `defaultAnswerData` is not applied if `cases` is
+    # defined and there are no matching cases. In this scenario, the next rule will be processed.
     #
     # @return [Array<OCI::Dns::Models::SteeringPolicyPriorityAnswerData>]
     attr_accessor :default_answer_data

data/lib/oci/dns/models/steering_policy_priority_rule_case.rb

@@ -6,9 +6,17 @@ require 'date'
 module OCI
   # SteeringPolicyPriorityRuleCase model.
   class Dns::Models::SteeringPolicyPriorityRuleCase # rubocop:disable Metrics/LineLength
+    # An expression that uses conditions at the time of a DNS query to indicate
+    # whether a case matches. Conditions may include the geographical location, IP
+    # subnet, or ASN the DNS query originated. **Example:** If you have an
+    # office that uses the subnet `192.0.2.0/24` you could use a `caseCondition`
+    # expression `query.client.subnet in ('192.0.2.0/24')` to define a case that
+    # matches queries from that office.
+    #
     # @return [String]
     attr_accessor :case_condition
 
+    # An array of `SteeringPolicyPriorityAnswerData` objects.
     # @return [Array<OCI::Dns::Models::SteeringPolicyPriorityAnswerData>]
     attr_accessor :answer_data
 

data/lib/oci/dns/models/steering_policy_rule.rb

@@ -5,23 +5,17 @@ require 'logger'
 
 # rubocop:disable Lint/UnneededCopDisableDirective
 module OCI
-  # Configuration for sorting and/or filtering the list of remaining candidate answers, subject to
-  # rule type and the values of type-specific parameters and/or data associated with answers.
+  # The configuration of the sorting and filtering behaviors in a steering policy. Rules can
+  # filter and sort answers based on weight, priority, endpoint health, and other data.
+  #
   #
   # A rule may optionally include a sequence of cases, each with an optional `caseCondition`
-  # expression.  If it does, the first case with a matching `caseCondition` or with no
-  # `caseCondition` at all is used to set rule parameter values and/or answer-associated data,
-  # and the rule will be ignored during processing of any request that does not match any case.
-  # Rules without a sequence of cases are processed unconditionally, and rules with an _empty_
-  # sequence of cases are **ignored** unconditionally.
+  # expression. Cases allow a sequence of conditions to be defined that will apply different
+  # parameters to the rule when the conditions are met. For more information about cases,
+  # see [Traffic Management API Guide](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).
   #
-  # Data is associated with answers one-by-one in a similar fashion\u2014for each answer, the first
-  # answerData item with a matching `answerCondition` or with no `answerCondition` at all is used
-  # to associate data with the answer, and the absence of any such item associates with the answer
-  # a default value.  Rule-level default answer data is always processed, but case-level answer
-  # data will override it on a per-answer basis.
   #
-  # To prevent empty responses, any attempt to filter away all answers is suppressed at runtime.
+  # **Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
   #
   # This class has direct subclasses. If you are using this class as input to a service operations then you should favor using a subclass over the base class
   class Dns::Models::SteeringPolicyRule # rubocop:disable Metrics/LineLength
@@ -34,22 +28,32 @@ module OCI
       RULE_TYPE_UNKNOWN_ENUM_VALUE = 'UNKNOWN_ENUM_VALUE'.freeze
     ].freeze
 
-    # Your description of the rule's purpose and/or behavior.
+    # A user-defined description of the rule's purpose or behavior.
     # @return [String]
     attr_accessor :description
 
     # **[Required]** The type of a rule determines its sorting/filtering behavior.
-    # - FILTER rules filter the list of answers (e.g., to remove those with hosts that are down
-    #   for maintenance). Answers remain if and only if their associated data is `true`.
-    # - HEALTH rules remove answers from the list if their `rdata` matches a target in the
+    # * `FILTER` - Filters the list of answers based on their defined boolean data. Answers remain
+    #   only if their `shouldKeep` value is `true`.
+    #
+    #
+    # * `HEALTH` - Removes answers from the list if their `rdata` matches a target in the
     #   health check monitor referenced by the steering policy and the target is reported down.
-    # - WEIGHTED rules probabilistically move answers with greater associated integer data to
-    #   the beginning of the list.
-    # - PRIORITY rules sort answers by associated integer data, moving those with the lowest
-    #   values to the beginning of the list without changing the relative order of those with
-    #   the same value.
-    # - LIMIT rules filter away answers that are too far down the list. Parameter \"count\"
-    #   specifies how many answers to keep.
+    #
+    #
+    # * `WEIGHTED` - Uses a number between 0 and 255 to determine how often an answer will be served
+    #   in relation to other answers. Anwers with a higher weight will be served more frequently.
+    #
+    #
+    # * `PRIORITY` - Uses a defined rank value of answers to determine which answer to serve,
+    #   moving those with the lowest values to the beginning of the list without changing the
+    #   relative order of those with the same value. Answers can be given a value between `0` and `255`.
+    #
+    #
+    # * `LIMIT` - Filters answers that are too far down the list. Parameter `defaultCount`
+    #   specifies how many answers to keep. **Example:** If `defaultCount` has a value of `2` and
+    #   there are five answers left, when the `LIMIT` rule is processed, only the first two answers
+    #   will remain in the list.
     #
     # @return [String]
     attr_reader :rule_type

data/lib/oci/dns/models/steering_policy_summary.rb

@@ -7,7 +7,7 @@ require 'logger'
 module OCI
   # A DNS steering policy.
   #
-  # *Warning:* Oracle recommends that you avoid using any confidential information when you supply string values using the API.
+  # **Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.
   #
   class Dns::Models::SteeringPolicySummary # rubocop:disable Metrics/LineLength
     TEMPLATE_ENUM = [
@@ -32,80 +32,90 @@ module OCI
     # @return [String]
     attr_accessor :compartment_id
 
-    # A user-friendly name for the steering policy.
-    # Does not have to be unique, and it's changeable.
+    # A user-friendly name for the steering policy. Does not have to be unique and can be changed.
     # Avoid entering confidential information.
     #
     # @return [String]
     attr_accessor :display_name
 
-    # The Time To Live for responses from the steering policy, in seconds.
+    # The Time To Live (TTL) for responses from the steering policy, in seconds.
     # If not specified during creation, a value of 30 seconds will be used.
     #
     # @return [Integer]
     attr_accessor :ttl
 
     # The OCID of the health check monitor providing health data about the answers of the
-    # steering policy.
-    # A steering policy answer with `rdata` matching a monitored endpoint will use the health
-    # data of that endpoint.
-    # A steering policy answer with `rdata` not matching any monitored endpoint will be assumed
-    # healthy.
+    # steering policy. A steering policy answer with `rdata` matching a monitored endpoint
+    # will use the health data of that endpoint. A steering policy answer with `rdata` not
+    # matching any monitored endpoint will be assumed healthy.
+    #
+    #
+    # **Note:** To use the Health Check monitoring feature in a steering policy, a monitor
+    # must be created using the Health Checks service first. For more information on how to
+    # create a monitor, please see [Managing Health Checks](https://docs.cloud.oracle.com/iaas/Content/HealthChecks/Tasks/managinghealthchecks.htm).
     #
     # @return [String]
     attr_accessor :health_check_monitor_id
 
-    # The common pattern (or lack thereof) to which the steering policy adheres. This
-    # value restricts the possible configurations of rules, but thereby supports
-    # specifically tailored interfaces. Values other than \"CUSTOM\" require the rules to
-    # begin with an unconditional FILTER that keeps answers contingent upon
-    # `answer.isDisabled != true`, followed
-    # _if and only if the policy references a health check monitor_ by an unconditional
-    # HEALTH rule, and require the last rule to be an unconditional LIMIT.
-    # What must precede the LIMIT rule is determined by the template value:
-    # - FAILOVER requires exactly an unconditional PRIORITY rule that ranks answers by pool.
-    #   Each answer pool must have a unique priority value assigned to it. Answer data must
-    #   be defined in the `defaultAnswerData` property for the rule and the `cases` property
-    #   must not be defined.
-    # - LOAD_BALANCE requires exactly an unconditional WEIGHTED rule that shuffles answers
-    #   by name. Answer data must be defined in the `defaultAnswerData` property for the
-    #   rule and the `cases` property must not be defined.
-    # - ROUTE_BY_GEO requires exactly one PRIORITY rule that ranks answers by pool using the
-    #   geographical location of the client as a condition. Within that rule you may only
-    #   use `query.client.geoKey` in the `caseCondition` expressions for defining the cases.
-    #   For each case in the PRIORITY rule each answer pool must have a unique priority
-    #   value assigned to it. Answer data can only be defined within cases and
-    #   `defaultAnswerData` cannot be used in the PRIORITY rule.
-    # - ROUTE_BY_ASN requires exactly one PRIORITY rule that ranks answers by pool using the
-    #   ASN of the client as a condition. Within that rule you may only use
-    #   `query.client.asn` in the `caseCondition` expressions for defining the cases.
-    #   For each case in the PRIORITY rule each answer pool must have a unique priority
-    #   value assigned to it. Answer data can only be defined within cases and
-    #   `defaultAnswerData` cannot be used in the PRIORITY rule.
-    # - ROUTE_BY_IP requires exactly one PRIORITY rule that ranks answers by pool using the
-    #   IP subnet of the client as a condition. Within that rule you may only use
-    #   `query.client.address` in the `caseCondition` expressions for defining the cases.
-    #   For each case in the PRIORITY rule each answer pool must have a unique priority
-    #   value assigned to it. Answer data can only be defined within cases and
-    #   `defaultAnswerData` cannot be used in the PRIORITY rule.
-    # - CUSTOM allows an arbitrary configuration of rules.
-    #
-    # For an existing steering policy, the template value may be changed to any of the
-    # supported options but the resulting policy must conform to the requirements for the
-    # new template type or else a Bad Request error will be returned.
+    # A set of predefined rules based on the desired purpose of the steering policy. Each
+    # template utilizes Traffic Management's rules in a different order to produce the desired
+    # results when answering DNS queries.
+    #
+    #
+    # **Example:** The `FAILOVER` template determines answers by filtering the policy's answers
+    # using the `FILTER` rule first, then the following rules in succession: `HEALTH`, `PRIORITY`,
+    # and `LIMIT`. This gives the domain dynamic failover capability.
+    #
+    #
+    # It is **strongly recommended** to use a template other than `CUSTOM` when creating
+    # a steering policy.
+    #
+    #
+    # All templates require the rule order to begin with an unconditional `FILTER` rule that keeps
+    # answers contingent upon `answer.isDisabled != true`, except for `CUSTOM`. A defined
+    # `HEALTH` rule must follow the `FILTER` rule if the policy references a `healthCheckMonitorId`.
+    # The last rule of a template must must be a `LIMIT` rule. For more information about templates
+    # and code examples, see [Traffic Management API Guide](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).
+    #
+    # **Template Types**
+    #
+    # * `FAILOVER` - Uses health check information on your endpoints to determine which DNS answers
+    # to serve. If an endpoint fails a health check, the answer for that endpoint will be removed
+    # from the list of available answers until the endpoint is detected as healthy.
+    #
+    #
+    # * `LOAD_BALANCE` - Distributes web traffic to specified endpoints based on defined weights.
+    #
+    #
+    # * `ROUTE_BY_GEO` - Answers DNS queries based on the query's geographic location. For a list of geographic
+    # locations to route by, see [Traffic Management Geographic Locations](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Reference/trafficmanagementgeo.htm).
+    #
+    #
+    # * `ROUTE_BY_ASN` - Answers DNS queries based on the query's originating ASN.
+    #
+    #
+    # * `ROUTE_BY_IP` - Answers DNS queries based on the query's IP address.
+    #
+    #
+    # * `CUSTOM` - Allows a customized configuration of rules.
     #
     # @return [String]
     attr_reader :template
 
-    # Simple key-value pair that is applied without any predefined name, type, or scope.
+    # Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace.
     # For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
-    # Example: `{\"bar-key\": \"value\"}`
+    #
+    #
+    # **Example:** `{\"Department\": \"Finance\"}`
     #
     # @return [Hash<String, String>]
     attr_accessor :freeform_tags
 
-    # Usage of predefined tag keys. These predefined keys are scoped to a namespace.
-    # Example: `{\"foo-namespace\": {\"bar-key\": \"value\"}}`
+    # Defined tags for this resource. Each key is predefined and scoped to a namespace.
+    # For more information, see [Resource Tags](https://docs.cloud.oracle.com/Content/General/Concepts/resourcetags.htm).
+    #
+    #
+    # **Example:** `{\"Operations\": {\"CostCenter\": \"42\"}}`
     #
     # @return [Hash<String, Hash<String, Object>>]
     attr_accessor :defined_tags
@@ -118,8 +128,7 @@ module OCI
     # @return [String]
     attr_accessor :id
 
-    # The date and time the resource was created in \"YYYY-MM-ddThh:mmZ\" format
-    # with a Z offset, as defined by RFC 3339.
+    # The date and time the resource was created, expressed in RFC 3339 timestamp format.
     #
     # **Example:** `2016-07-22T17:23:59:60Z`
     #