Specify accepted types for UpsertRows values

.generator/schemas/v2/openapi.yaml

@@ -6968,15 +6968,21 @@ components:
     BatchUpsertRowsRequestDataAttributes:
       description: Attributes containing row data values for row creation or update
         operations.
+      example:
+        values:
+          age: 25
+          example_key_value: primary_key_value
+          name: row_name
       properties:
         values:
           additionalProperties:
-            x-required-field: true
-          description: Key-value pairs representing row data, where keys are field
-            names from the schema.
-          example:
-            example_key_value: primary_key_value
-            name: row_name
+            oneOf:
+            - type: string
+            - format: int32
+              maximum: 2147483647
+              type: integer
+          description: Key-value pairs representing row data, where keys are schema
+            field names and values match the corresponding column types.
           type: object
       required:
       - values
@@ -69084,9 +69090,6 @@ paths:
         operator: OR
         permissions:
         - incident_read
-      x-unstable: '**Note**: This endpoint is in Preview.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
     post:
       description: Create an impact for an incident.
       operationId: CreateIncidentImpact
@@ -69130,9 +69133,6 @@ paths:
         operator: OR
         permissions:
         - incident_write
-      x-unstable: '**Note**: This endpoint is in Preview.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/incidents/{incident_id}/impacts/{impact_id}:
     delete:
       description: Delete an incident impact.
@@ -69163,9 +69163,6 @@ paths:
         operator: OR
         permissions:
         - incident_write
-      x-unstable: '**Note**: This endpoint is in Preview.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v2/incidents/{incident_id}/relationships/integrations:
     get:
       description: Get all integration metadata for an incident.

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/incidents.feature

@@ -806,16 +806,14 @@ Feature: Incidents
 
   @generated @skip @team:DataDog/incident-app
   Scenario: List an incident's impacts returns "Bad Request" response
-    Given operation "ListIncidentImpacts" enabled
-    And new "ListIncidentImpacts" request
+    Given new "ListIncidentImpacts" request
     And request contains "incident_id" parameter from "REPLACE.ME"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/incident-app
   Scenario: List an incident's impacts returns "Not Found" response
-    Given operation "ListIncidentImpacts" enabled
-    And new "ListIncidentImpacts" request
+    Given new "ListIncidentImpacts" request
     And request contains "incident_id" parameter from "REPLACE.ME"
     When the request is sent
     Then the response status is 404 Not Found

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

@@ -249,14 +249,12 @@ def initialize
             "v2.update_deployment_gate": false,
             "v2.update_deployment_rule": false,
             "v2.create_incident": false,
-            "v2.create_incident_impact": false,
             "v2.create_incident_integration": false,
             "v2.create_incident_notification_rule": false,
             "v2.create_incident_notification_template": false,
             "v2.create_incident_todo": false,
             "v2.create_incident_type": false,
             "v2.delete_incident": false,
-            "v2.delete_incident_impact": false,
             "v2.delete_incident_integration": false,
             "v2.delete_incident_notification_rule": false,
             "v2.delete_incident_notification_template": false,
@@ -269,7 +267,6 @@ def initialize
             "v2.get_incident_todo": false,
             "v2.get_incident_type": false,
             "v2.list_incident_attachments": false,
-            "v2.list_incident_impacts": false,
             "v2.list_incident_integrations": false,
             "v2.list_incident_notification_rules": false,
             "v2.list_incident_notification_templates": false,

lib/datadog_api_client/v2/api/incidents_api.rb

@@ -114,12 +114,6 @@ def create_incident_impact(incident_id, body, opts = {})
     # @option opts [Array<IncidentImpactRelatedObject>] :include Specifies which related resources should be included in the response.
     # @return [Array<(IncidentImpactResponse, Integer, Hash)>] IncidentImpactResponse data, response status code and response headers
     def create_incident_impact_with_http_info(incident_id, body, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.create_incident_impact".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.create_incident_impact")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.create_incident_impact"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: IncidentsAPI.create_incident_impact ...'
@@ -639,12 +633,6 @@ def delete_incident_impact(incident_id, impact_id, opts = {})
     # @param opts [Hash] the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
     def delete_incident_impact_with_http_info(incident_id, impact_id, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.delete_incident_impact".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.delete_incident_impact")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.delete_incident_impact"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: IncidentsAPI.delete_incident_impact ...'
@@ -1601,12 +1589,6 @@ def list_incident_impacts(incident_id, opts = {})
     # @option opts [Array<IncidentImpactRelatedObject>] :include Specifies which related resources should be included in the response.
     # @return [Array<(IncidentImpactsResponse, Integer, Hash)>] IncidentImpactsResponse data, response status code and response headers
     def list_incident_impacts_with_http_info(incident_id, opts = {})
-      unstable_enabled = @api_client.config.unstable_operations["v2.list_incident_impacts".to_sym]
-      if unstable_enabled
-        @api_client.config.logger.warn format("Using unstable operation '%s'", "v2.list_incident_impacts")
-      else
-        raise DatadogAPIClient::APIError.new(message: format("Unstable operation '%s' is disabled", "v2.list_incident_impacts"))
-      end
 
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: IncidentsAPI.list_incident_impacts ...'

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 schema field names and values match the corresponding column types.
     attr_reader :values
 
     attr_accessor :additional_properties