Regenerate client from commit 384636b of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v2/openapi.yaml

@@ -28735,6 +28735,31 @@ components:
         - bucket_name
         - bucket_region
       type: object
+    DataObservabilityMonitorRunStatus:
+      description: The status of a data observability monitor run.
+      enum:
+        - pending
+        - ok
+        - warn
+        - alert
+        - error
+      example: pending
+      type: string
+      x-enum-varnames:
+        - PENDING
+        - OK
+        - WARN
+        - ALERT
+        - ERROR
+    DataObservabilityMonitorRunType:
+      default: monitor_run
+      description: The JSON:API resource type for a data observability monitor run.
+      enum:
+        - monitor_run
+      example: monitor_run
+      type: string
+      x-enum-varnames:
+        - MONITOR_RUN
     DataRelationshipsTeams:
       description: Associates teams with this schedule in a data structure.
       properties:
@@ -39045,6 +39070,42 @@ components:
         meta:
           $ref: "#/components/schemas/DataDeletionResponseMeta"
       type: object
+    GetDataObservabilityMonitorRunStatusResponse:
+      description: The response for getting the status of a data observability monitor run.
+      properties:
+        data:
+          $ref: "#/components/schemas/GetDataObservabilityMonitorRunStatusResponseData"
+      required:
+        - data
+      type: object
+    GetDataObservabilityMonitorRunStatusResponseAttributes:
+      description: The attributes of a data observability monitor run status response.
+      properties:
+        error_message:
+          description: Error message describing why the monitor run failed. Only present when status is error.
+          example: "run completed but produced no metric data"
+          type: string
+        status:
+          $ref: "#/components/schemas/DataObservabilityMonitorRunStatus"
+      required:
+        - status
+      type: object
+    GetDataObservabilityMonitorRunStatusResponseData:
+      description: The data object for a data observability monitor run status response.
+      properties:
+        attributes:
+          $ref: "#/components/schemas/GetDataObservabilityMonitorRunStatusResponseAttributes"
+        id:
+          description: The unique identifier of the monitor run.
+          example: "abc123def456"
+          type: string
+        type:
+          $ref: "#/components/schemas/DataObservabilityMonitorRunType"
+      required:
+        - id
+        - type
+        - attributes
+      type: object
     GetDeviceAttributes:
       description: The device attributes
       properties:
@@ -77898,6 +77959,27 @@ components:
             $ref: "#/components/schemas/RumRetentionFilterData"
           type: array
       type: object
+    RunDataObservabilityMonitorResponse:
+      description: The response returned when a data observability monitor run is triggered.
+      properties:
+        data:
+          $ref: "#/components/schemas/RunDataObservabilityMonitorResponseData"
+      required:
+        - data
+      type: object
+    RunDataObservabilityMonitorResponseData:
+      description: The data object returned when a data observability monitor run is triggered.
+      properties:
+        id:
+          description: The unique identifier of the monitor run.
+          example: "abc123def456"
+          type: string
+        type:
+          $ref: "#/components/schemas/DataObservabilityMonitorRunType"
+      required:
+        - id
+        - type
+      type: object
     RunHistoricalJobRequest:
       description: Run a historical job request.
       properties:
@@ -124777,6 +124859,105 @@ paths:
       x-unstable: |-
         **Note**: This endpoint is in preview and is subject to change.
         If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
+  /api/v2/data-observability/monitors/runs/{run_id}/status:
+    get:
+      description: Retrieves the current status of a data observability monitor run. Poll this endpoint after triggering a run to determine when evaluation is complete.
+      operationId: GetDataObservabilityMonitorRunStatus
+      parameters:
+        - description: The ID of the monitor run to retrieve status for.
+          example: "abc123def456"
+          in: path
+          name: run_id
+          required: true
+          schema:
+            type: string
+      responses:
+        "200":
+          content:
+            application/json:
+              examples:
+                default:
+                  value:
+                    data:
+                      attributes:
+                        status: ok
+                      id: "abc123def456"
+                      type: monitor_run
+              schema:
+                $ref: "#/components/schemas/GetDataObservabilityMonitorRunStatusResponse"
+          description: OK
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Not Found
+        "429":
+          $ref: "#/components/responses/TooManyRequestsResponse"
+      security:
+        - apiKeyAuth: []
+          appKeyAuth: []
+        - AuthZ:
+            - data_observability_monitors_write
+            - monitors_write
+      summary: Get data observability monitor run status
+      tags:
+        - Data Observability
+      x-unstable: |-
+        **Note**: This endpoint is in preview and is subject to change.
+        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
+  /api/v2/data-observability/monitors/{monitor_id}/run:
+    post:
+      description: Manually triggers a run for a data observability monitor. Only monitors that are not scheduled (manually-runnable) can be triggered this way.
+      operationId: RunDataObservabilityMonitor
+      parameters:
+        - description: The ID of the data observability monitor to run.
+          example: 12345
+          in: path
+          name: monitor_id
+          required: true
+          schema:
+            format: int64
+            type: integer
+      responses:
+        "200":
+          content:
+            application/json:
+              examples:
+                default:
+                  value:
+                    data:
+                      id: "abc123def456"
+                      type: monitor_run
+              schema:
+                $ref: "#/components/schemas/RunDataObservabilityMonitorResponse"
+          description: OK
+        "400":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Bad Request
+        "404":
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/JSONAPIErrorResponse"
+          description: Not Found
+        "429":
+          $ref: "#/components/responses/TooManyRequestsResponse"
+      security:
+        - apiKeyAuth: []
+          appKeyAuth: []
+        - AuthZ:
+            - data_observability_monitors_write
+            - monitors_write
+      summary: Run a data observability monitor
+      tags:
+        - Data Observability
+      x-unstable: |-
+        **Note**: This endpoint is in preview and is subject to change.
+        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
   /api/v2/datasets:
     get:
       description: Get all datasets that have been configured for an organization.
@@ -186518,6 +186699,8 @@ tags:
   - description: |-
       The Data Deletion API allows the user to target and delete data from the allowed products. It's currently enabled for Logs and RUM and depends on `logs_delete_data` and `rum_delete_data` permissions respectively.
     name: Data Deletion
+  - description: Manage and run data observability monitors.
+    name: Data Observability
   - description: |-
       Data Access Controls in Datadog is a feature that allows administrators and access managers to regulate
       access to sensitive data. By defining Restricted Datasets, you can ensure that only specific teams or roles can

docs/datadog_api_client.v2.api.rst

@@ -291,6 +291,13 @@ datadog\_api\_client.v2.api.data\_deletion\_api module
    :members:
    :show-inheritance:
 
+datadog\_api\_client.v2.api.data\_observability\_api module
+-----------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.api.data_observability_api
+   :members:
+   :show-inheritance:
+
 datadog\_api\_client.v2.api.datasets\_api module
 ------------------------------------------------
 

docs/datadog_api_client.v2.model.rst

@@ -10987,6 +10987,20 @@ datadog\_api\_client.v2.model.data\_export\_config module
    :members:
    :show-inheritance:
 
+datadog\_api\_client.v2.model.data\_observability\_monitor\_run\_status module
+------------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.data_observability_monitor_run_status
+   :members:
+   :show-inheritance:
+
+datadog\_api\_client.v2.model.data\_observability\_monitor\_run\_type module
+----------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.data_observability_monitor_run_type
+   :members:
+   :show-inheritance:
+
 datadog\_api\_client.v2.model.data\_relationships\_teams module
 ---------------------------------------------------------------
 
@@ -15789,6 +15803,27 @@ datadog\_api\_client.v2.model.get\_data\_deletions\_response\_body module
    :members:
    :show-inheritance:
 
+datadog\_api\_client.v2.model.get\_data\_observability\_monitor\_run\_status\_response module
+---------------------------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.get_data_observability_monitor_run_status_response
+   :members:
+   :show-inheritance:
+
+datadog\_api\_client.v2.model.get\_data\_observability\_monitor\_run\_status\_response\_attributes module
+---------------------------------------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.get_data_observability_monitor_run_status_response_attributes
+   :members:
+   :show-inheritance:
+
+datadog\_api\_client.v2.model.get\_data\_observability\_monitor\_run\_status\_response\_data module
+---------------------------------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.get_data_observability_monitor_run_status_response_data
+   :members:
+   :show-inheritance:
+
 datadog\_api\_client.v2.model.get\_device\_attributes module
 ------------------------------------------------------------
 
@@ -33548,6 +33583,20 @@ datadog\_api\_client.v2.model.rum\_warning module
    :members:
    :show-inheritance:
 
+datadog\_api\_client.v2.model.run\_data\_observability\_monitor\_response module
+--------------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.run_data_observability_monitor_response
+   :members:
+   :show-inheritance:
+
+datadog\_api\_client.v2.model.run\_data\_observability\_monitor\_response\_data module
+--------------------------------------------------------------------------------------
+
+.. automodule:: datadog_api_client.v2.model.run_data_observability_monitor_response_data
+   :members:
+   :show-inheritance:
+
 datadog\_api\_client.v2.model.run\_historical\_job\_request module
 ------------------------------------------------------------------
 

src/datadog_api_client/configuration.py

@@ -482,6 +482,8 @@ def __init__(
                 "v2.update_dashboard_secure_embed": False,
                 "v2.get_dashboard_usage": False,
                 "v2.list_dashboards_usage": False,
+                "v2.get_data_observability_monitor_run_status": False,
+                "v2.run_data_observability_monitor": False,
                 "v2.create_dataset": False,
                 "v2.delete_dataset": False,
                 "v2.get_all_datasets": False,