Merge master into datadog-api-spec/test/jmallma/event-intake-v2

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-11-15 19:35:10.102953",
-            "spec_repo_commit": "ad80112e"
+            "regenerated": "2024-11-19 18:07:22.354004",
+            "spec_repo_commit": "f858f395"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-11-15 19:35:10.121640",
-            "spec_repo_commit": "ad80112e"
+            "regenerated": "2024-11-19 18:07:22.372908",
+            "spec_repo_commit": "f858f395"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -36442,7 +36442,8 @@ tags:
   name: Logs
 - description: 'Manage configuration of [log indexes](https://docs.datadoghq.com/logs/indexes/).
 
-    You need an API and application key with Admin rights to interact with this endpoint.'
+    You need an API and non-scoped application key with Admin rights to interact with
+    these endpoints.'
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/indexes/
@@ -36454,11 +36455,12 @@ tags:
     about processors can be found in the\n  [processors documentation](https://docs.datadoghq.com/logs/log_configuration/processors/?tab=api#lookup-processor).\n\n-
     For more information about Pipelines, see the\n  [pipeline documentation](https://docs.datadoghq.com/logs/log_configuration/pipelines).\n\n**Notes:**\n\nThese
     endpoints are only available for admin users.\nMake sure to use an application
-    key created by an admin.\n\n**Grok parsing rules may effect JSON output and require\nreturned
-    data to be configured before using in a request.**\nFor example, if you are using
-    the data returned from a\nrequest for another request body, and have a parsing
-    rule\nthat uses a regex pattern like `\\s` for spaces, you will\nneed to configure
-    all escaped spaces as `%{space}` to use\nin the body data."
+    key created by an admin with no applied scopes.\n\n**Grok parsing rules may effect
+    JSON output and require\nreturned data to be configured before using in a request.**\nFor
+    example, if you are using the data returned from a\nrequest for another request
+    body, and have a parsing rule\nthat uses a regex pattern like `\\s` for spaces,
+    you will\nneed to configure all escaped spaces as `%{space}` to use\nin the body
+    data."
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/log_configuration

.generator/schemas/v2/openapi.yaml

@@ -27189,6 +27189,7 @@ components:
             security_monitoring_rules_read: Read Detection Rules.
             security_monitoring_rules_write: Create and edit Detection Rules.
             security_monitoring_signals_read: View Security Signals.
+            security_monitoring_signals_write: Edit Security Signals.
             security_monitoring_suppressions_read: Read Rule Suppressions.
             security_monitoring_suppressions_write: Write Rule Suppressions.
             security_pipelines_read: View Security Pipelines.
@@ -40801,11 +40802,16 @@ paths:
       security:
       - apiKeyAuth: []
         appKeyAuth: []
-      - AuthZ: []
+      - AuthZ:
+        - security_monitoring_rules_write
       summary: Run a historical job
       tags:
       - Security Monitoring
       x-codegen-request-body-name: body
+      x-permission:
+        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.'
@@ -40835,11 +40841,16 @@ paths:
       security:
       - apiKeyAuth: []
         appKeyAuth: []
-      - AuthZ: []
+      - AuthZ:
+        - security_monitoring_signals_write
       summary: Convert a job result to a signal
       tags:
       - Security Monitoring
       x-codegen-request-body-name: body
+      x-permission:
+        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.'
@@ -40897,10 +40908,15 @@ paths:
       security:
       - apiKeyAuth: []
         appKeyAuth: []
-      - AuthZ: []
+      - AuthZ:
+        - security_monitoring_rules_read
       summary: Get a job's details
       tags:
       - Security Monitoring
+      x-permission:
+        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.'
@@ -40928,10 +40944,15 @@ paths:
       security:
       - apiKeyAuth: []
         appKeyAuth: []
-      - AuthZ: []
+      - AuthZ:
+        - security_monitoring_rules_write
       summary: Cancel a historical job
       tags:
       - Security Monitoring
+      x-permission:
+        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.'
@@ -43809,7 +43830,11 @@ tags:
 
     See the [Archives Page](https://app.datadoghq.com/logs/pipelines/archives)
 
-    for a list of the archives currently configured in Datadog.'
+    for a list of the archives currently configured in Datadog.
+
+
+    You need an API and non-scoped application key with Admin rights to interact with
+    these endpoints.'
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/archives/
@@ -43828,8 +43853,11 @@ tags:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/log_configuration/forwarding_custom_destinations/
   name: Logs Custom Destinations
-- description: Manage configuration of [log-based metrics](https://app.datadoghq.com/logs/pipelines/generate-metrics)
+- description: 'Manage configuration of [log-based metrics](https://app.datadoghq.com/logs/pipelines/generate-metrics)
     for your organization.
+
+    You need an API and non-scoped application key with Admin rights to interact with
+    these endpoints.'
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/logs_to_metrics/

src/datadogV1/api/api_logs_indexes.rs

@@ -63,7 +63,7 @@ pub enum UpdateLogsIndexOrderError {
 }
 
 /// Manage configuration of [log indexes](<https://docs.datadoghq.com/logs/indexes/>).
-/// You need an API and application key with Admin rights to interact with this endpoint.
+/// You need an API and non-scoped application key with Admin rights to interact with these endpoints.
 #[derive(Debug, Clone)]
 pub struct LogsIndexesAPI {
     config: datadog::Configuration,

src/datadogV1/api/api_logs_pipelines.rs

@@ -86,7 +86,7 @@ pub enum UpdateLogsPipelineOrderError {
 /// **Notes:**
 ///
 /// These endpoints are only available for admin users.
-/// Make sure to use an application key created by an admin.
+/// Make sure to use an application key created by an admin with no applied scopes.
 ///
 /// **Grok parsing rules may effect JSON output and require
 /// returned data to be configured before using in a request.**

src/datadogV2/api/api_logs_archives.rs

@@ -94,6 +94,8 @@ pub enum UpdateLogsArchiveOrderError {
 ///
 /// See the [Archives Page](<https://app.datadoghq.com/logs/pipelines/archives>)
 /// for a list of the archives currently configured in Datadog.
+///
+/// You need an API and non-scoped application key with Admin rights to interact with these endpoints.
 #[derive(Debug, Clone)]
 pub struct LogsArchivesAPI {
     config: datadog::Configuration,

src/datadogV2/api/api_logs_metrics.rs

@@ -51,6 +51,7 @@ pub enum UpdateLogsMetricError {
 }
 
 /// Manage configuration of [log-based metrics](<https://app.datadoghq.com/logs/pipelines/generate-metrics>) for your organization.
+/// You need an API and non-scoped application key with Admin rights to interact with these endpoints.
 #[derive(Debug, Clone)]
 pub struct LogsMetricsAPI {
     config: datadog::Configuration,

tests/scenarios/features/v1/logs_indexes.feature

@@ -2,7 +2,8 @@
 Feature: Logs Indexes
   Manage configuration of [log
   indexes](https://docs.datadoghq.com/logs/indexes/). You need an API and
-  application key with Admin rights to interact with this endpoint.
+  non-scoped application key with Admin rights to interact with these
+  endpoints.
 
   Background:
     Given a valid "apiKeyAuth" key in the system

tests/scenarios/features/v1/logs_pipelines.feature

@@ -10,12 +10,13 @@ Feature: Logs Pipelines
   s/?tab=api#lookup-processor).  - For more information about Pipelines, see
   the   [pipeline documentation](https://docs.datadoghq.com/logs/log_configu
   ration/pipelines).  **Notes:**  These endpoints are only available for
-  admin users. Make sure to use an application key created by an admin.
-  **Grok parsing rules may effect JSON output and require returned data to
-  be configured before using in a request.** For example, if you are using
-  the data returned from a request for another request body, and have a
-  parsing rule that uses a regex pattern like `\s` for spaces, you will need
-  to configure all escaped spaces as `%{space}` to use in the body data.
+  admin users. Make sure to use an application key created by an admin with
+  no applied scopes.  **Grok parsing rules may effect JSON output and
+  require returned data to be configured before using in a request.** For
+  example, if you are using the data returned from a request for another
+  request body, and have a parsing rule that uses a regex pattern like `\s`
+  for spaces, you will need to configure all escaped spaces as `%{space}` to
+  use in the body data.
 
   Background:
     Given a valid "apiKeyAuth" key in the system

tests/scenarios/features/v2/logs_archives.feature

@@ -2,7 +2,9 @@
 Feature: Logs Archives
   Archives forward all the logs ingested to a cloud storage system.  See the
   [Archives Page](https://app.datadoghq.com/logs/pipelines/archives) for a
-  list of the archives currently configured in Datadog.
+  list of the archives currently configured in Datadog.  You need an API and
+  non-scoped application key with Admin rights to interact with these
+  endpoints.
 
   Background:
     Given a valid "apiKeyAuth" key in the system