Regenerate client from commit fe3756c4 of spec repo

Author: ci.datadog-api-spec

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-04 20:19:34.024681",
-            "spec_repo_commit": "3909ab62"
+            "regenerated": "2025-04-06 16:06:34.726233",
+            "spec_repo_commit": "fe3756c4"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-04-04 20:19:34.040447",
-            "spec_repo_commit": "3909ab62"
+            "regenerated": "2025-04-06 16:06:34.742117",
+            "spec_repo_commit": "fe3756c4"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -50645,9 +50645,6 @@ paths:
       summary: List historical jobs
       tags:
       - Security Monitoring
-      x-unstable: '**Note**: This endpoint is in beta and may be subject to changes.
-
-        Please check the documentation regularly for updates.'
     post:
       description: Run a historical job.
       operationId: RunHistoricalJob
@@ -50687,9 +50684,6 @@ paths:
         operator: OR
         permissions:
         - security_monitoring_rules_write
-      x-unstable: '**Note**: This endpoint is in beta and may be subject to changes.
-
-        Please check the documentation regularly for updates.'
   /api/v2/siem-historical-detections/jobs/signal_convert:
     post:
       description: Convert a job result to a signal.
@@ -50721,9 +50715,6 @@ paths:
         operator: OR
         permissions:
         - security_monitoring_signals_write
-      x-unstable: '**Note**: This endpoint is in beta and may be subject to changes.
-
-        Please check the documentation regularly for updates.'
   /api/v2/siem-historical-detections/jobs/{job_id}:
     delete:
       description: Delete an existing job.
@@ -50752,9 +50743,6 @@ paths:
       summary: Delete an existing job
       tags:
       - Security Monitoring
-      x-unstable: '**Note**: This endpoint is in beta and may be subject to changes.
-
-        Please check the documentation regularly for updates.'
     get:
       description: Get a job's details.
       operationId: GetHistoricalJob
@@ -50787,9 +50775,6 @@ paths:
         operator: OR
         permissions:
         - security_monitoring_rules_read
-      x-unstable: '**Note**: This endpoint is in beta and may be subject to changes.
-
-        Please check the documentation regularly for updates.'
   /api/v2/siem-historical-detections/jobs/{job_id}/cancel:
     patch:
       description: Cancel a historical job.
@@ -50823,9 +50808,6 @@ paths:
         operator: OR
         permissions:
         - security_monitoring_rules_write
-      x-unstable: '**Note**: This endpoint is in beta and may be subject to changes.
-
-        Please check the documentation regularly for updates.'
   /api/v2/slo/report:
     post:
       description: 'Create a job to generate an SLO report. The report job is processed

examples/v2/security-monitoring/CancelHistoricalJob.rb

@@ -1,10 +1,6 @@
 # Cancel a historical job returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.cancel_historical_job".to_sym] = true
-  config.unstable_operations["v2.run_historical_job".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 # there is a valid "historical_job" in the system

examples/v2/security-monitoring/ConvertJobResultToSignal.rb

@@ -1,9 +1,6 @@
 # Convert a job result to a signal returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.convert_job_result_to_signal".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 body = DatadogAPIClient::V2::ConvertJobResultsToSignalsRequest.new({

examples/v2/security-monitoring/DeleteHistoricalJob.rb

@@ -1,8 +1,5 @@
 # Delete an existing job returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.delete_historical_job".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 api_instance.delete_historical_job("job_id")

examples/v2/security-monitoring/GetHistoricalJob.rb

@@ -1,10 +1,6 @@
 # Get a job's details returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.get_historical_job".to_sym] = true
-  config.unstable_operations["v2.run_historical_job".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 # there is a valid "historical_job" in the system

examples/v2/security-monitoring/ListHistoricalJobs.rb

@@ -1,10 +1,6 @@
 # List historical jobs returns "OK" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.list_historical_jobs".to_sym] = true
-  config.unstable_operations["v2.run_historical_job".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 # there is a valid "historical_job" in the system

examples/v2/security-monitoring/RunHistoricalJob.rb

@@ -1,9 +1,6 @@
 # Run a historical job returns "Status created" response
 
 require "datadog_api_client"
-DatadogAPIClient.configure do |config|
-  config.unstable_operations["v2.run_historical_job".to_sym] = true
-end
 api_instance = DatadogAPIClient::V2::SecurityMonitoringAPI.new
 
 body = DatadogAPIClient::V2::RunHistoricalJobRequest.new({

features/v2/security_monitoring.feature

@@ -11,33 +11,28 @@ Feature: Security Monitoring
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Cancel a historical job returns "Bad Request" response
-    Given operation "CancelHistoricalJob" enabled
-    And new "CancelHistoricalJob" request
+    Given new "CancelHistoricalJob" request
     And request contains "job_id" parameter with value "inva-lid"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Cancel a historical job returns "Conflict" response
-    Given operation "CancelHistoricalJob" enabled
-    And new "CancelHistoricalJob" request
+    Given new "CancelHistoricalJob" request
     And request contains "job_id" parameter from "REPLACE.ME"
     When the request is sent
     Then the response status is 409 Conflict
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Cancel a historical job returns "Not Found" response
-    Given operation "CancelHistoricalJob" enabled
-    And new "CancelHistoricalJob" request
+    Given new "CancelHistoricalJob" request
     And request contains "job_id" parameter with value "8e2a37fb-b0c8-4761-a7f0-0a8d6a98ba93"
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Cancel a historical job returns "OK" response
-    Given operation "CancelHistoricalJob" enabled
-    And operation "RunHistoricalJob" enabled
-    And new "CancelHistoricalJob" request
+    Given new "CancelHistoricalJob" request
     And there is a valid "historical_job" in the system
     And request contains "job_id" parameter from "historical_job.data.id"
     When the request is sent
@@ -93,24 +88,21 @@ Feature: Security Monitoring
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Convert a job result to a signal returns "Bad Request" response
-    Given operation "ConvertJobResultToSignal" enabled
-    And new "ConvertJobResultToSignal" request
+    Given new "ConvertJobResultToSignal" request
     And body with value {"data": {"attributes": {"jobResultIds": [""], "notifications": [""], "signalMessage": "A large number of failed login attempts.", "signalSeverity": "critical"}, "type": "historicalDetectionsJobResultSignalConversion"}}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Convert a job result to a signal returns "Not Found" response
-    Given operation "ConvertJobResultToSignal" enabled
-    And new "ConvertJobResultToSignal" request
+    Given new "ConvertJobResultToSignal" request
     And body with value {"data": {"attributes": {"jobResultIds": [""], "notifications": [""], "signalMessage": "A large number of failed login attempts.", "signalSeverity": "critical"}, "type": "historicalDetectionsJobResultSignalConversion"}}
     When the request is sent
     Then the response status is 404 Not Found
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Convert a job result to a signal returns "OK" response
-    Given operation "ConvertJobResultToSignal" enabled
-    And new "ConvertJobResultToSignal" request
+    Given new "ConvertJobResultToSignal" request
     And body with value {"data": {"attributes": {"jobResultIds": [""], "notifications": [""], "signalMessage": "A large number of failed login attempts.", "signalSeverity": "critical"}, "type": "historicalDetectionsJobResultSignalConversion"}}
     When the request is sent
     Then the response status is 204 OK
@@ -410,32 +402,28 @@ Feature: Security Monitoring
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Delete an existing job returns "Bad Request" response
-    Given operation "DeleteHistoricalJob" enabled
-    And new "DeleteHistoricalJob" request
+    Given new "DeleteHistoricalJob" request
     And request contains "job_id" parameter with value "inva-lid"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Delete an existing job returns "Conflict" response
-    Given operation "DeleteHistoricalJob" enabled
-    And new "DeleteHistoricalJob" request
+    Given new "DeleteHistoricalJob" request
     And request contains "job_id" parameter from "REPLACE.ME"
     When the request is sent
     Then the response status is 409 Conflict
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Delete an existing job returns "Not Found" response
-    Given operation "DeleteHistoricalJob" enabled
-    And new "DeleteHistoricalJob" request
+    Given new "DeleteHistoricalJob" request
     And request contains "job_id" parameter with value "8e2a37fb-b0c8-4761-a7f0-0a8d6a98ba93"
     When the request is sent
     Then the response status is 404 Not Found
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: Delete an existing job returns "OK" response
-    Given operation "DeleteHistoricalJob" enabled
-    And new "DeleteHistoricalJob" request
+    Given new "DeleteHistoricalJob" request
     And request contains "job_id" parameter from "REPLACE.ME"
     When the request is sent
     Then the response status is 204 OK
@@ -519,25 +507,21 @@ Feature: Security Monitoring
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Get a job's details returns "Bad Request" response
-    Given operation "GetHistoricalJob" enabled
-    And new "GetHistoricalJob" request
+    Given new "GetHistoricalJob" request
     And request contains "job_id" parameter with value "inva-lid"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Get a job's details returns "Not Found" response
-    Given operation "GetHistoricalJob" enabled
-    And new "GetHistoricalJob" request
+    Given new "GetHistoricalJob" request
     And request contains "job_id" parameter with value "8e2a37fb-b0c8-4761-a7f0-0a8d6a98ba93"
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Get a job's details returns "OK" response
-    Given operation "GetHistoricalJob" enabled
-    And operation "RunHistoricalJob" enabled
-    And new "GetHistoricalJob" request
+    Given new "GetHistoricalJob" request
     And there is a valid "historical_job" in the system
     And request contains "job_id" parameter from "historical_job.data.id"
     When the request is sent
@@ -801,16 +785,13 @@ Feature: Security Monitoring
 
   @generated @skip @team:DataDog/k9-cloud-security-platform
   Scenario: List historical jobs returns "Bad Request" response
-    Given operation "ListHistoricalJobs" enabled
-    And new "ListHistoricalJobs" request
+    Given new "ListHistoricalJobs" request
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: List historical jobs returns "OK" response
-    Given operation "ListHistoricalJobs" enabled
-    And operation "RunHistoricalJob" enabled
-    And new "ListHistoricalJobs" request
+    Given new "ListHistoricalJobs" request
     And there is a valid "historical_job" in the system
     And request contains "filter[query]" parameter with value "id:{{historical_job.data.id}}"
     When the request is sent
@@ -1006,24 +987,21 @@ Feature: Security Monitoring
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Run a historical job returns "Bad Request" response
-    Given operation "RunHistoricalJob" enabled
-    And new "RunHistoricalJob" request
+    Given new "RunHistoricalJob" request
     And body with value {"data":{"type":"historicalDetectionsJobCreate","attributes":{"jobDefinition":{"type":"log_detection","name":"Excessive number of failed attempts.","queries":[{"query":"source:non_existing_src_weekend","aggregation":"count","groupByFields":[],"distinctFields":[]}],"cases":[{"name":"Condition 1","status":"info","notifications":[],"condition":"a > 1"}],"options":{"keepAlive":3600,"maxSignalDuration":86400,"evaluationWindow":900},"message":"A large number of failed login attempts.","tags":[],"from":1730387522611,"to":1730391122611,"index":"non_existing_index"}}}}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Run a historical job returns "Not Found" response
-    Given operation "RunHistoricalJob" enabled
-    And new "RunHistoricalJob" request
+    Given new "RunHistoricalJob" request
     And body with value {"data": { "type": "historicalDetectionsJobCreate", "attributes": {"fromRule": {"caseIndex": 0, "from": 1730201035064, "id": "non-existng", "index": "main", "notifications": [], "to": 1730204635115}}}}
     When the request is sent
     Then the response status is 404 Not Found
 
   @team:DataDog/k9-cloud-security-platform
   Scenario: Run a historical job returns "Status created" response
-    Given operation "RunHistoricalJob" enabled
-    And new "RunHistoricalJob" request
+    Given new "RunHistoricalJob" request
     And body with value {"data":{"type":"historicalDetectionsJobCreate","attributes":{"jobDefinition":{"type":"log_detection","name":"Excessive number of failed attempts.","queries":[{"query":"source:non_existing_src_weekend","aggregation":"count","groupByFields":[],"distinctFields":[]}],"cases":[{"name":"Condition 1","status":"info","notifications":[],"condition":"a > 1"}],"options":{"keepAlive":3600,"maxSignalDuration":86400,"evaluationWindow":900},"message":"A large number of failed login attempts.","tags":[],"from":1730387522611,"to":1730387532611,"index":"main"}}}}
     When the request is sent
     Then the response status is 201 Status created

lib/datadog_api_client/configuration.rb

@@ -231,19 +231,13 @@ def initialize
             "v2.update_aws_account": false,
             "v2.list_aws_logs_services": false,
             "v2.get_aggregated_connections": false,
-            "v2.cancel_historical_job": false,
-            "v2.convert_job_result_to_signal": false,
-            "v2.delete_historical_job": false,
             "v2.get_finding": false,
-            "v2.get_historical_job": false,
             "v2.get_rule_version_history": false,
             "v2.get_sbom": false,
             "v2.list_findings": false,
-            "v2.list_historical_jobs": false,
             "v2.list_vulnerabilities": false,
             "v2.list_vulnerable_assets": false,
             "v2.mute_findings": false,
-            "v2.run_historical_job": false,
             "v2.create_scorecard_outcomes_batch": false,
             "v2.create_scorecard_rule": false,
             "v2.delete_scorecard_rule": false,