Patch open Logs routes with logs_read_config permission (#2368)

Co-authored-by: ci.datadog-api-spec <[email protected]>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-24 20:40:50.935454",
-            "spec_repo_commit": "c6ec55eb"
+            "regenerated": "2025-01-27 15:14:15.089106",
+            "spec_repo_commit": "333d42be"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-01-24 20:40:50.958148",
-            "spec_repo_commit": "c6ec55eb"
+            "regenerated": "2025-01-27 15:14:15.104235",
+            "spec_repo_commit": "333d42be"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -28362,8 +28362,9 @@ paths:
       tags:
       - Logs Indexes
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: 'This endpoint updates the index order of your organization.
 
@@ -28435,8 +28436,9 @@ paths:
       tags:
       - Logs Indexes
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     post:
       description: Creates a new index. Returns the Index object passed in the request
         body when the request is successful.
@@ -28513,6 +28515,10 @@ paths:
       summary: Get an index
       tags:
       - Logs Indexes
+      x-permission:
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: "Update an index as identified by its name.\nReturns the Index
         object passed in the request body when the request is successful.\n\nUsing
@@ -28587,8 +28593,9 @@ paths:
       tags:
       - Logs Pipelines
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: 'Update the order of your pipelines. Since logs are processed sequentially,
         reordering a pipeline may change
@@ -28669,8 +28676,9 @@ paths:
       tags:
       - Logs Pipelines
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     post:
       description: Create a pipeline in your organization.
       operationId: CreateLogsPipeline
@@ -28784,8 +28792,9 @@ paths:
       tags:
       - Logs Pipelines
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: "Update a given pipeline configuration to change it\u2019s processors
         or their order.\n\n**Note**: Using this method updates your pipeline configuration
@@ -36578,10 +36587,7 @@ tags:
 - description: Search your logs and send them to your Datadog platform over HTTP.
     See the [Log Management page](https://docs.datadoghq.com/logs/) for more information.
   name: Logs
-- description: 'Manage configuration of [log indexes](https://docs.datadoghq.com/logs/indexes/).
-
-    You need an API and non-scoped application key with Admin rights to interact with
-    these endpoints.'
+- description: Manage configuration of [log indexes](https://docs.datadoghq.com/logs/indexes/).
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/indexes/
@@ -36591,14 +36597,12 @@ tags:
     page](https://app.datadoghq.com/logs/pipelines)\n  for a list of the pipelines
     and processors currently configured in web UI.\n\n- Additional API-related information
     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 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."
+    For more information about Pipelines, see the\n  [pipeline documentation](https://docs.datadoghq.com/logs/log_configuration/pipelines).\n\n**Notes:**\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

@@ -38944,8 +38944,9 @@ paths:
       tags:
       - Logs Archives
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     put:
       description: 'Update the order of your archives. Since logs are processed sequentially,
         reordering an archive may change
@@ -39272,8 +39273,9 @@ paths:
       - Logs Archives
       x-codegen-request-body-name: body
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     post:
       description: Adds a read role to an archive. ([Roles API](https://docs.datadoghq.com/api/v2/roles/))
       operationId: AddReadRoleToArchive
@@ -39343,6 +39345,7 @@ paths:
         operator: OR
         permissions:
         - logs_read_data
+        - logs_read_config
     post:
       description: Create a custom destination in your organization.
       operationId: CreateLogsCustomDestination
@@ -39427,6 +39430,7 @@ paths:
         operator: OR
         permissions:
         - logs_read_data
+        - logs_read_config
     patch:
       description: Update the given fields of a specific custom destination in your
         organization.
@@ -39484,8 +39488,9 @@ paths:
       tags:
       - Logs Metrics
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     post:
       description: 'Create a metric based on your ingested logs in your organization.
 
@@ -39566,8 +39571,9 @@ paths:
       tags:
       - Logs Metrics
       x-permission:
-        operator: OPEN
-        permissions: []
+        operator: OR
+        permissions:
+        - logs_read_config
     patch:
       description: 'Update a specific log-based metric from your organization.
 
@@ -49742,11 +49748,7 @@ tags:
 
     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.'
+    for a list of the archives currently configured in Datadog.'
   externalDocs:
     description: Find out more at
     url: https://docs.datadoghq.com/logs/archives/
@@ -49765,11 +49767,8 @@ 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/datadog_api_client/v1/api/logs_indexes_api.py

@@ -16,7 +16,6 @@
 class LogsIndexesApi:
     """
     Manage configuration of `log indexes <https://docs.datadoghq.com/logs/indexes/>`_.
-    You need an API and non-scoped application key with Admin rights to interact with these endpoints.
     """
 
     def __init__(self, api_client=None):

src/datadog_api_client/v1/api/logs_pipelines_api.py

@@ -31,9 +31,6 @@ class LogsPipelinesApi:
 
     **Notes:**
 
-    These endpoints are only available for 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

src/datadog_api_client/v2/api/logs_archives_api.py

@@ -21,8 +21,6 @@ class LogsArchivesApi:
 
     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.
     """
 
     def __init__(self, api_client=None):

src/datadog_api_client/v2/api/logs_metrics_api.py

@@ -16,7 +16,6 @@
 class LogsMetricsApi:
     """
     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.
     """
 
     def __init__(self, api_client=None):

tests/v1/features/logs_indexes.feature

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

tests/v1/features/logs_pipelines.feature

@@ -9,14 +9,12 @@ Feature: Logs Pipelines
   documentation](https://docs.datadoghq.com/logs/log_configuration/processor
   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 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.
+  ration/pipelines).  **Notes:**  **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/v2/features/logs_archives.feature

@@ -2,9 +2,7 @@
 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.  You need an API and
-  non-scoped application key with Admin rights to interact with these
-  endpoints.
+  list of the archives currently configured in Datadog.
 
   Background:
     Given a valid "apiKeyAuth" key in the system