Regenerate client from commit 526ff73 of spec repo

Author: ci.datadog-api-spec

.generator/schemas/v1/openapi.yaml

@@ -11798,7 +11798,8 @@ components:
         The default option results in different behavior depending on the monitor query type.
         For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
         For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-        This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        It is also required for metric monitors that use `scheduling_options.custom_schedule`.
       enum:
         - "default"
         - "show_no_data"

.generator/schemas/v2/openapi.yaml

@@ -64968,6 +64968,9 @@ components:
             description: The ID of a component whose output is used as input for this destination.
             type: string
           type: array
+        tls:
+          $ref: "#/components/schemas/ObservabilityPipelineTls"
+          description: Configuration for TLS encryption.
         type:
           $ref: "#/components/schemas/ObservabilityPipelineCloudPremDestinationType"
       required:

src/datadog_api_client/v1/model/monitor_options.py

@@ -289,7 +289,8 @@ def __init__(
             The default option results in different behavior depending on the monitor query type.
             For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
             For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-            This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+            This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+            It is also required for metric monitors that use ``scheduling_options.custom_schedule``.
         :type on_missing_data: OnMissingDataOption, optional
 
         :param renotify_interval: The number of minutes after the last notification before a monitor re-notifies on the current status.

src/datadog_api_client/v1/model/on_missing_data_option.py

@@ -18,7 +18,8 @@ class OnMissingDataOption(ModelSimple):
         The default option results in different behavior depending on the monitor query type.
         For monitors using Count queries, an empty monitor evaluation is treated as 0 and is compared to the threshold conditions.
         For monitors using any query type other than Count, for example Gauge, Measure, or Rate, the monitor shows the last known status.
-        This option is only available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        This option is available for APM Trace Analytics, Audit Trail, CI, Error Tracking, Event, Logs, and RUM monitors.
+        It is also required for metric monitors that use `scheduling_options.custom_schedule`.
 
     :param value: Must be one of ["default", "show_no_data", "show_and_notify_no_data", "resolve"].
     :type value: str

src/datadog_api_client/v2/model/observability_pipeline_cloud_prem_destination.py

@@ -15,6 +15,7 @@
 
 if TYPE_CHECKING:
     from datadog_api_client.v2.model.observability_pipeline_buffer_options import ObservabilityPipelineBufferOptions
+    from datadog_api_client.v2.model.observability_pipeline_tls import ObservabilityPipelineTls
     from datadog_api_client.v2.model.observability_pipeline_cloud_prem_destination_type import (
         ObservabilityPipelineCloudPremDestinationType,
     )
@@ -33,6 +34,7 @@ class ObservabilityPipelineCloudPremDestination(ModelNormal):
     @cached_property
     def openapi_types(_):
         from datadog_api_client.v2.model.observability_pipeline_buffer_options import ObservabilityPipelineBufferOptions
+        from datadog_api_client.v2.model.observability_pipeline_tls import ObservabilityPipelineTls
         from datadog_api_client.v2.model.observability_pipeline_cloud_prem_destination_type import (
             ObservabilityPipelineCloudPremDestinationType,
         )
@@ -42,6 +44,7 @@ def openapi_types(_):
             "endpoint_url_key": (str,),
             "id": (str,),
             "inputs": ([str],),
+            "tls": (ObservabilityPipelineTls,),
             "type": (ObservabilityPipelineCloudPremDestinationType,),
         }
 
@@ -50,6 +53,7 @@ def openapi_types(_):
         "endpoint_url_key": "endpoint_url_key",
         "id": "id",
         "inputs": "inputs",
+        "tls": "tls",
         "type": "type",
     }
 
@@ -66,6 +70,7 @@ def __init__(
             UnsetType,
         ] = unset,
         endpoint_url_key: Union[str, UnsetType] = unset,
+        tls: Union[ObservabilityPipelineTls, UnsetType] = unset,
         **kwargs,
     ):
         """
@@ -85,13 +90,18 @@ def __init__(
         :param inputs: A list of component IDs whose output is used as the ``input`` for this component.
         :type inputs: [str]
 
+        :param tls: Configuration for enabling TLS encryption between the pipeline component and external services.
+        :type tls: ObservabilityPipelineTls, optional
+
         :param type: The destination type. The value should always be ``cloud_prem``.
         :type type: ObservabilityPipelineCloudPremDestinationType
         """
         if buffer is not unset:
             kwargs["buffer"] = buffer
         if endpoint_url_key is not unset:
             kwargs["endpoint_url_key"] = endpoint_url_key
+        if tls is not unset:
+            kwargs["tls"] = tls
         super().__init__(kwargs)
 
         self_.id = id

tests/v1/features/monitors.feature

@@ -119,7 +119,7 @@ Feature: Monitors
     And the response "name" is equal to "{{ unique }}"
     And the response "query" is equal to "avg(current_1mo):avg:system.load.5{*} > 0.5"
 
-  @team:DataDog/monitor-app
+  @oncall-page:monitor-app @team:DataDog/monitor-app
   Scenario: Create a metric monitor with a custom schedule returns "OK" response
     Given new "CreateMonitor" request
     And body with value {"message":"some message Notify: @hipchat-channel","name":"{{ unique }}","query":"avg(current_1mo):avg:system.load.5{*} > 0.5","tags":[],"options":{"thresholds":{"critical":0.5},"notify_audit":false,"include_tags":false,"on_missing_data":"default","scheduling_options":{"evaluation_window":{"day_starts":"04:00", "month_starts":1},"custom_schedule":{"recurrences":[{"rrule":"FREQ=DAILY;INTERVAL=1","timezone":"America/Los_Angeles","start":"2024-10-26T09:13:00"}]}}},"type":"query alert", "draft_status": "published"}