diff --git a/.apigentools-info b/.apigentools-info index e9b7d0c88..809fd386a 100644 --- a/.apigentools-info +++ b/.apigentools-info @@ -4,13 +4,13 @@ "spec_versions": { "v1": { "apigentools_version": "1.6.6", - "regenerated": "2024-11-18 20:16:41.226338", - "spec_repo_commit": "1939caa6" + "regenerated": "2024-11-19 18:07:22.354004", + "spec_repo_commit": "f858f395" }, "v2": { "apigentools_version": "1.6.6", - "regenerated": "2024-11-18 20:16:41.245434", - "spec_repo_commit": "1939caa6" + "regenerated": "2024-11-19 18:07:22.372908", + "spec_repo_commit": "f858f395" } } } \ No newline at end of file diff --git a/.generator/schemas/v1/openapi.yaml b/.generator/schemas/v1/openapi.yaml index 1594c9cda..bcc5ab30e 100644 --- a/.generator/schemas/v1/openapi.yaml +++ b/.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 diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index 4b6b5ea52..2b6a098d5 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.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/ diff --git a/src/datadogV1/api/api_logs_indexes.rs b/src/datadogV1/api/api_logs_indexes.rs index 4054e0e86..202cb3fa9 100644 --- a/src/datadogV1/api/api_logs_indexes.rs +++ b/src/datadogV1/api/api_logs_indexes.rs @@ -63,7 +63,7 @@ pub enum UpdateLogsIndexOrderError { } /// Manage configuration of [log 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, diff --git a/src/datadogV1/api/api_logs_pipelines.rs b/src/datadogV1/api/api_logs_pipelines.rs index 339e06c65..d7371955f 100644 --- a/src/datadogV1/api/api_logs_pipelines.rs +++ b/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.** diff --git a/src/datadogV2/api/api_logs_archives.rs b/src/datadogV2/api/api_logs_archives.rs index 2f841fbcc..54db77bd5 100644 --- a/src/datadogV2/api/api_logs_archives.rs +++ b/src/datadogV2/api/api_logs_archives.rs @@ -94,6 +94,8 @@ pub enum UpdateLogsArchiveOrderError { /// /// See the [Archives Page]() /// 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, diff --git a/src/datadogV2/api/api_logs_metrics.rs b/src/datadogV2/api/api_logs_metrics.rs index efbc60591..7f2731332 100644 --- a/src/datadogV2/api/api_logs_metrics.rs +++ b/src/datadogV2/api/api_logs_metrics.rs @@ -51,6 +51,7 @@ pub enum UpdateLogsMetricError { } /// Manage configuration of [log-based 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, diff --git a/tests/scenarios/features/v1/logs_indexes.feature b/tests/scenarios/features/v1/logs_indexes.feature index 76b2d87a4..f449dcbb5 100644 --- a/tests/scenarios/features/v1/logs_indexes.feature +++ b/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 diff --git a/tests/scenarios/features/v1/logs_pipelines.feature b/tests/scenarios/features/v1/logs_pipelines.feature index 640b3cef9..f7a689170 100644 --- a/tests/scenarios/features/v1/logs_pipelines.feature +++ b/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 diff --git a/tests/scenarios/features/v2/logs_archives.feature b/tests/scenarios/features/v2/logs_archives.feature index 1e1057c34..a3c89c042 100644 --- a/tests/scenarios/features/v2/logs_archives.feature +++ b/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 diff --git a/tests/scenarios/features/v2/logs_metrics.feature b/tests/scenarios/features/v2/logs_metrics.feature index c2488458b..080d8b83b 100644 --- a/tests/scenarios/features/v2/logs_metrics.feature +++ b/tests/scenarios/features/v2/logs_metrics.feature @@ -2,7 +2,8 @@ Feature: Logs Metrics Manage configuration of [log-based metrics](https://app.datadoghq.com/logs/pipelines/generate-metrics) for - your organization. + your organization. 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