Clarify need of non-scoped app keys for some log endpoints (#2270)

* Regenerate client from commit f858f395 of spec repo

* pre-commit fixes

---------

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": "2024-11-18 20:17:00.322824",
-            "spec_repo_commit": "1939caa6"
+            "regenerated": "2024-11-19 18:07:17.903802",
+            "spec_repo_commit": "f858f395"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-11-18 20:17:00.340566",
-            "spec_repo_commit": "1939caa6"
+            "regenerated": "2024-11-19 18:07:17.921127",
+            "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

@@ -43830,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/
@@ -43849,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/datadog_api_client/v1/api/logs_indexes_api.py

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

src/datadog_api_client/v1/api/logs_pipelines_api.py

@@ -32,7 +32,7 @@ class LogsPipelinesApi:
     **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/datadog_api_client/v2/api/logs_archives_api.py

@@ -21,6 +21,8 @@ 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,6 +16,7 @@
 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

@@ -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/v1/features/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/v2/features/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