oci 2.5.3 → 2.5.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e50aec53657bc50fd4f4a486a9c9271162ee5ca8359b122826daaf9ba84cebae
-  data.tar.gz: d55e454f869a09abb01e1b8999ed92c357af9af1c5f624f33526e292c2749a26
+  metadata.gz: 9eacad662893aaafea6e5c3364a1303cff336b9333263b447dee38537b5fe669
+  data.tar.gz: ae519c919e675327ce111c60203e8b1fabe9d49583dc48f9a4dc9c7f0fbd0ec8
 SHA512:
-  metadata.gz: 521e46b9785d4abb0293bd312f7163a4f4277ef251b39c7ff44cf768bd242df89ad9d513ee693f1af0a8bcb7e454bce3f9004c82d19f914d0bcd739ffbdcdab7
-  data.tar.gz: 975fd8d0735c0a0e9fbf291ca3cdd8884879ae9e5125b69ede5bf8132cc3d8fec108f3bdc5ad21d6ac2307e811dc7933b8cacd0ccb5338dac0cf4373a4928527
+  metadata.gz: '0929254b79d4b39f5105b828b3cf226cca77201d5eabd2261160feaa2553c8454fb683d6d585492ed106c7c0c6d62767baabb2989c6c08560f0fe1f76c6ce321'
+  data.tar.gz: 55fccd1687e793019bd66d0d2d12da9738c02b193e1f484043829efaa2d60132dd1a0c11c7721958a32a71b2eb136280525d5dc0915d9bc5572b895ddc171e69

data/README.md

@@ -1,5 +1,5 @@
 # Oracle Cloud Infrastructure Ruby SDK
-**Version 2.5.3**
+**Version 2.5.4**
 
 This topic describes how to install, configure, and use the Oracle Cloud Infrastructure Ruby SDK.
 

data/lib/oci/dns/dns_client.rb

@@ -109,7 +109,8 @@ module OCI
     # rubocop:disable Metrics/MethodLength, Layout/EmptyLines
 
 
-    # Creates a new steering policy in the specified compartment.
+    # Creates a new steering policy in the specified compartment. For more information on
+    # creating policies with templates, see [Traffic Management API Guide](https://docs.cloud.oracle.com/iaas/Content/TrafficManagement/Concepts/trafficmanagementapi.htm).
     #
     # @param [OCI::Dns::Models::CreateSteeringPolicyDetails] create_steering_policy_details Details for creating a new steering policy.
     # @param [Hash] opts the optional parameters
@@ -169,9 +170,12 @@ module OCI
     # rubocop:disable Metrics/MethodLength, Layout/EmptyLines
 
 
-    # Creates a new attachment between a steering policy and a domain.
+    # Creates a new attachment between a steering policy and a domain, giving the
+    # policy permission to answer queries for the specified domain. A steering policy must
+    # be attached to a domain for the policy to answer DNS queries for that domain.
+    #
     # For the purposes of access control, the attachment is automatically placed
-    # into the same compartment as the containing zone of the domain.
+    # into the same compartment as the domain's zone.
     #
     # @param [OCI::Dns::Models::CreateSteeringPolicyAttachmentDetails] create_steering_policy_attachment_details Details for creating a new steering policy attachment.
     # @param [Hash] opts the optional parameters
@@ -430,7 +434,8 @@ module OCI
 
     # Deletes the specified steering policy.
     # A `204` response indicates that the delete has been successful.
-    # Deletion will fail if the policy is attached to any zones.
+    # Deletion will fail if the policy is attached to any zones. To detach a
+    # policy from a zone, see `DeleteSteeringPolicyAttachment`.
     #
     # @param [String] steering_policy_id The OCID of the target steering policy.
     # @param [Hash] opts the optional parameters
@@ -1123,7 +1128,7 @@ module OCI
     #   (case-insensitive) contains the provided value.
     #
     # @option opts [String] :health_check_monitor_id Search by health check monitor OCID.
-    #   Will match any resource whose health check monitor id matches the provided value.
+    #   Will match any resource whose health check monitor ID matches the provided value.
     #
     # @option opts [DateTime] :time_created_greater_than_or_equal_to An [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) timestamp that states
     #   all returned resources were created on or after the indicated time.
@@ -1131,11 +1136,11 @@ module OCI
     # @option opts [DateTime] :time_created_less_than An [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) timestamp that states
     #   all returned resources were created before the indicated time.
     #
-    # @option opts [String] :template Search by template type.
+    # @option opts [String] :template Search by steering template type.
     #   Will match any resource whose template type matches the provided value.
     #
     # @option opts [String] :lifecycle_state The state of a resource.
-    # @option opts [String] :sort_by The field by which to sort steering policies. (default to timeCreated)
+    # @option opts [String] :sort_by The field by which to sort steering policies. If unspecified, defaults to `timeCreated`. (default to timeCreated)
     #   Allowed values are: displayName, timeCreated, template
     # @option opts [String] :sort_order The order to sort the resources.
     #
@@ -1222,10 +1227,10 @@ module OCI
     # @option opts [String] :id The OCID of a resource.
     # @option opts [String] :display_name The displayName of a resource.
     # @option opts [String] :steering_policy_id Search by steering policy OCID.
-    #   Will match any resource whose steering policy id matches the provided value.
+    #   Will match any resource whose steering policy ID matches the provided value.
     #
     # @option opts [String] :zone_id Search by zone OCID.
-    #   Will match any resource whose zone id matches the provided value.
+    #   Will match any resource whose zone ID matches the provided value.
     #
     # @option opts [String] :domain Search by domain.
     #   Will match any record whose domain (case-insensitive) equals the provided value.
@@ -1240,7 +1245,7 @@ module OCI
     #   all returned resources were created before the indicated time.
     #
     # @option opts [String] :lifecycle_state The state of a resource.
-    # @option opts [String] :sort_by The field by which to sort steering policy attachments. (default to timeCreated)
+    # @option opts [String] :sort_by The field by which to sort steering policy attachments. If unspecified, defaults to `timeCreated`. (default to timeCreated)
     #   Allowed values are: displayName, timeCreated, domainName
     # @option opts [String] :sort_order The order to sort the resources.
     #
@@ -1420,7 +1425,11 @@ module OCI
     # rubocop:disable Metrics/MethodLength, Layout/EmptyLines
 
 
-    # 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.
+    # 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.
+    #
     # @param [String] zone_name_or_id The name or OCID of the target zone.
     # @param [String] domain The target fully-qualified domain name (FQDN) within the target zone.
     # @param [OCI::Dns::Models::PatchDomainRecordsDetails] patch_domain_records_details Operations describing how to modify the collection of records.
@@ -1794,7 +1803,7 @@ module OCI
     # rubocop:disable Metrics/MethodLength, Layout/EmptyLines
 
 
-    # Updates the specified steering policy with your new information.
+    # Updates the configuration of the specified steering policy.
     #
     # @param [String] steering_policy_id The OCID of the target steering policy.
     # @param [OCI::Dns::Models::UpdateSteeringPolicyDetails] update_steering_policy_details New data for the steering policy.

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

@@ -5,12 +5,9 @@ require 'date'
 # rubocop:disable Lint/UnneededCopDisableDirective
 module OCI
   # The body for defining 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.
-  # The attachment will cover every rtype that matches the rtype of an answer in its policy, and
-  # will cover all address rtypes (e.g., A and AAAA) if the policy includes at least one CNAME
-  # answer.
-  # A domain can have at most 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::CreateSteeringPolicyAttachmentDetails # rubocop:disable Metrics/LineLength
     # **[Required]** The OCID of the attached steering policy.
@@ -26,7 +23,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]

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

@@ -6,7 +6,7 @@ require 'date'
 module OCI
   # The body for defining a new 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::CreateSteeringPolicyDetails # rubocop:disable Metrics/LineLength
     TEMPLATE_ENUM = [
@@ -22,80 +22,90 @@ module OCI
     # @return [String]
     attr_accessor :compartment_id
 
-    # **[Required]** A user-friendly name for the steering policy.
-    # Does not have to be unique, and it's changeable.
+    # **[Required]** 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
 
-    # **[Required]** 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.
+    # **[Required]** 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
@@ -105,9 +115,10 @@ module OCI
     # @return [Array<OCI::Dns::Models::SteeringPolicyAnswer>]
     attr_accessor :answers
 
-    # The pipeline of rules that will be processed in sequence to reduce the pool of answers
+    # The series of rules that will be processed in sequence to reduce the pool of answers
     # to a response for any given request.
     #
+    #
     # The first rule receives a shuffled list of all answers, and every other rule receives
     # the list of answers emitted by the one preceding it. The last rule populates the
     # response.

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

@@ -6,7 +6,7 @@ require 'date'
 module OCI
   # The body for defining a new zone.
   #
-  # *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::CreateZoneDetails # rubocop:disable Metrics/LineLength
     ZONE_TYPE_ENUM = [
@@ -27,15 +27,20 @@ module OCI
     # @return [String]
     attr_accessor :compartment_id
 
-    # 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

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

@@ -4,7 +4,9 @@ require 'date'
 
 # rubocop:disable Lint/UnneededCopDisableDirective
 module OCI
-  # A DNS resource record. For more information about DNS records, see [RFC 1034](https://tools.ietf.org/html/rfc1034#section-3.6).
+  # A DNS resource record. For more information, see
+  # [Supported DNS Resource Record Types](https://docs.cloud.oracle.com/iaas/Content/DNS/Reference/supporteddnsresource.htm).
+  #
   class Dns::Models::Record # rubocop:disable Metrics/LineLength
     # The fully qualified domain name where the record can be located.
     #

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

@@ -58,18 +58,22 @@ module OCI
 
     # A description of how a record relates to a PATCH operation.
     #
+    #
     # - `REQUIRE` indicates a precondition that record data **must** already exist.
     # - `PROHIBIT` indicates a precondition that record data **must not** already exist.
     # - `ADD` indicates that record data **must** exist after successful application.
     # - `REMOVE` indicates that record data **must not** exist after successful application.
     #
+    #
     #   **Note:** `ADD` and `REMOVE` operations can succeed even if
     #   they require no changes when applied, such as when the described
     #   records are already present or absent.
     #
+    #
     #   **Note:** `ADD` and `REMOVE` operations can describe changes for
     #   more than one record.
     #
+    #
     #   **Example:** `{ \"domain\": \"www.example.com\", \"rtype\": \"AAAA\", \"ttl\": 60 }`
     #   specifies a new TTL for every record in the www.example.com AAAA RRSet.
     #

data/lib/oci/dns/models/steering_policy.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::SteeringPolicy # 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
@@ -115,9 +125,10 @@ module OCI
     # @return [Array<OCI::Dns::Models::SteeringPolicyAnswer>]
     attr_accessor :answers
 
-    # The pipeline of rules that will be processed in sequence to reduce the pool of answers
+    # The series of rules that will be processed in sequence to reduce the pool of answers
     # to a response for any given request.
     #
+    #
     # The first rule receives a shuffled list of all answers, and every other rule receives
     # the list of answers emitted by the one preceding it. The last rule populates the
     # response.
@@ -133,8 +144,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`
     #