Regenerate client from commit 1b47950 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -6971,10 +6971,15 @@ components:
       properties:
         values:
           additionalProperties:
-            x-required-field: true
+            oneOf:
+            - type: string
+            - format: int32
+              maximum: 2147483647
+              type: integer
           description: Key-value pairs representing row data, where keys are field
-            names from the schema.
+            names from the schema, and values match the table's column types.
           example:
+            age: 25
             example_key_value: primary_key_value
             name: row_name
           type: object
@@ -67941,6 +67946,7 @@ paths:
             - us3.datadoghq.com
             - us5.datadoghq.com
             - ap1.datadoghq.com
+            - ap2.datadoghq.com
             - datadoghq.eu
             - ddog-gov.com
           subdomain:

examples/v2/reference-tables/UpsertRows.rb

@@ -8,7 +8,7 @@
     DatadogAPIClient::V2::BatchUpsertRowsRequestData.new({
       attributes: DatadogAPIClient::V2::BatchUpsertRowsRequestDataAttributes.new({
         values: {
-          example_key_value: "primary_key_value", name: "row_name",
+          age: 25, example_key_value: "primary_key_value", name: "row_name",
         },
       }),
       id: "primary_key_value",

features/v2/reference_tables.feature

@@ -148,22 +148,22 @@ Feature: Reference Tables
   Scenario: Upsert rows returns "Bad Request" response
     Given new "UpsertRows" request
     And request contains "id" parameter from "REPLACE.ME"
-    And body with value {"data": [{"attributes": {"values": {"example_key_value": "primary_key_value", "name": "row_name"}}, "id": "primary_key_value", "type": "row"}]}
+    And body with value {"data": [{"attributes": {"values": {"age": 25, "example_key_value": "primary_key_value", "name": "row_name"}}, "id": "primary_key_value", "type": "row"}]}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/redapl-experiences
   Scenario: Upsert rows returns "Not Found" response
     Given new "UpsertRows" request
     And request contains "id" parameter from "REPLACE.ME"
-    And body with value {"data": [{"attributes": {"values": {"example_key_value": "primary_key_value", "name": "row_name"}}, "id": "primary_key_value", "type": "row"}]}
+    And body with value {"data": [{"attributes": {"values": {"age": 25, "example_key_value": "primary_key_value", "name": "row_name"}}, "id": "primary_key_value", "type": "row"}]}
     When the request is sent
     Then the response status is 404 Not Found
 
   @generated @skip @team:DataDog/redapl-experiences
   Scenario: Upsert rows returns "Rows created or updated successfully" response
     Given new "UpsertRows" request
     And request contains "id" parameter from "REPLACE.ME"
-    And body with value {"data": [{"attributes": {"values": {"example_key_value": "primary_key_value", "name": "row_name"}}, "id": "primary_key_value", "type": "row"}]}
+    And body with value {"data": [{"attributes": {"values": {"age": 25, "example_key_value": "primary_key_value", "name": "row_name"}}, "id": "primary_key_value", "type": "row"}]}
     When the request is sent
     Then the response status is 200 Rows created or updated successfully

lib/datadog_api_client/configuration.rb

@@ -627,6 +627,7 @@ def operation_server_settings
                   "us3.datadoghq.com",
                   "us5.datadoghq.com",
                   "ap1.datadoghq.com",
+                  "ap2.datadoghq.com",
                   "datadoghq.eu",
                   "ddog-gov.com"
                 ]

lib/datadog_api_client/v2/models/batch_upsert_rows_request_data_attributes.rb

@@ -21,7 +21,7 @@ module DatadogAPIClient::V2
   class BatchUpsertRowsRequestDataAttributes
     include BaseGenericModel
 
-    # Key-value pairs representing row data, where keys are field names from the schema.
+    # Key-value pairs representing row data, where keys are field names from the schema, and values match the table's column types.
     attr_reader :values
 
     attr_accessor :additional_properties