Regenerate client from commit 6dc3341 of spec repo (#250)

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.4.1.dev2",
-            "regenerated": "2021-01-28 17:53:54.712855",
-            "spec_repo_commit": "f21827d"
+            "regenerated": "2021-01-29 07:52:53.496255",
+            "spec_repo_commit": "6dc3341"
         },
         "v2": {
             "apigentools_version": "1.4.1.dev2",
-            "regenerated": "2021-01-28 17:54:06.073746",
-            "spec_repo_commit": "f21827d"
+            "regenerated": "2021-01-29 07:53:05.627056",
+            "spec_repo_commit": "6dc3341"
         }
     }
 }

docs/v1/LogsApi.md

@@ -4,13 +4,13 @@ All URIs are relative to *https://api.datadoghq.com*
 
 Method | HTTP request | Description
 ------------- | ------------- | -------------
-[**list_logs**](LogsApi.md#list_logs) | **POST** /api/v1/logs-queries/list | Get a list of logs
+[**list_logs**](LogsApi.md#list_logs) | **POST** /api/v1/logs-queries/list | Search logs
 
 
 # **list_logs**
 > LogsListResponse list_logs(body)
 
-Get a list of logs
+Search logs
 
 List endpoint returns logs that match a log search query. [Results are paginated][1].  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives
 
@@ -56,7 +56,7 @@ with ApiClient(configuration) as api_client:
 
     # example passing only required values which don't have defaults set
     try:
-        # Get a list of logs
+        # Search logs
         api_response = api_instance.list_logs(body)
         pprint(api_response)
     except ApiException as e:

docs/v1/README.md

@@ -161,7 +161,7 @@ Class | Method | HTTP request | Description
 *KeyManagementApi* | [**list_application_keys**](KeyManagementApi.md#list_application_keys) | **GET** /api/v1/application_key | Get all application keys
 *KeyManagementApi* | [**update_api_key**](KeyManagementApi.md#update_api_key) | **PUT** /api/v1/api_key/{key} | Edit an API key
 *KeyManagementApi* | [**update_application_key**](KeyManagementApi.md#update_application_key) | **PUT** /api/v1/application_key/{key} | Edit an application key
-*LogsApi* | [**list_logs**](LogsApi.md#list_logs) | **POST** /api/v1/logs-queries/list | Get a list of logs
+*LogsApi* | [**list_logs**](LogsApi.md#list_logs) | **POST** /api/v1/logs-queries/list | Search logs
 *LogsIndexesApi* | [**create_logs_index**](LogsIndexesApi.md#create_logs_index) | **POST** /api/v1/logs/config/indexes | Create an index
 *LogsIndexesApi* | [**get_logs_index**](LogsIndexesApi.md#get_logs_index) | **GET** /api/v1/logs/config/indexes/{name} | Get an index
 *LogsIndexesApi* | [**get_logs_index_order**](LogsIndexesApi.md#get_logs_index_order) | **GET** /api/v1/logs/config/index-order | Get indexes order

docs/v2/LogsApi.md

@@ -5,8 +5,8 @@ All URIs are relative to *https://api.datadoghq.com*
 Method | HTTP request | Description
 ------------- | ------------- | -------------
 [**aggregate_logs**](LogsApi.md#aggregate_logs) | **POST** /api/v2/logs/analytics/aggregate | Aggregate events
-[**list_logs**](LogsApi.md#list_logs) | **POST** /api/v2/logs/events/search | Get a list of logs
-[**list_logs_get**](LogsApi.md#list_logs_get) | **GET** /api/v2/logs/events | Get a quick list of logs
+[**list_logs**](LogsApi.md#list_logs) | **POST** /api/v2/logs/events/search | Search logs
+[**list_logs_get**](LogsApi.md#list_logs_get) | **GET** /api/v2/logs/events | Get a list of logs
 
 
 # **aggregate_logs**
@@ -126,9 +126,9 @@ Name | Type | Description  | Notes
 # **list_logs**
 > LogsListResponse list_logs()
 
-Get a list of logs
+Search logs
 
-List endpoint returns logs that match a log search query. [Results are paginated][1].  Both this endpoint and the GET endpoint can be used interchangeably when listing logs.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives
+List endpoint returns logs that match a log search query. [Results are paginated][1].  Use this endpoint to build complex logs filtering and search.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives
 
 ### Example
 
@@ -179,7 +179,7 @@ with ApiClient(configuration) as api_client:
     # example passing only required values which don't have defaults set
     # and optional values
     try:
-        # Get a list of logs
+        # Search logs
         api_response = api_instance.list_logs(body=body)
         pprint(api_response)
     except ApiException as e:
@@ -217,9 +217,9 @@ Name | Type | Description  | Notes
 # **list_logs_get**
 > LogsListResponse list_logs_get()
 
-Get a quick list of logs
+Get a list of logs
 
-List endpoint returns logs that match a log search query. [Results are paginated][1].  Both this endpoint and the POST endpoint can be used interchangeably when listing logs.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives
+List endpoint returns logs that match a log search query. [Results are paginated][1].  Use this endpoint to see your latest logs.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives
 
 ### Example
 
@@ -260,7 +260,7 @@ with ApiClient(configuration) as api_client:
     # example passing only required values which don't have defaults set
     # and optional values
     try:
-        # Get a quick list of logs
+        # Get a list of logs
         api_response = api_instance.list_logs_get(filter_query=filter_query, filter_index=filter_index, filter_from=filter_from, filter_to=filter_to, sort=sort, page_cursor=page_cursor, page_limit=page_limit)
         pprint(api_response)
     except ApiException as e:

docs/v2/README.md

@@ -133,8 +133,8 @@ Class | Method | HTTP request | Description
 *KeyManagementApi* | [**update_application_key**](KeyManagementApi.md#update_application_key) | **PATCH** /api/v2/application_keys/{app_key_id} | Edit an application key
 *KeyManagementApi* | [**update_current_user_application_key**](KeyManagementApi.md#update_current_user_application_key) | **PATCH** /api/v2/current_user/application_keys/{app_key_id} | Edit an application key owned by current user
 *LogsApi* | [**aggregate_logs**](LogsApi.md#aggregate_logs) | **POST** /api/v2/logs/analytics/aggregate | Aggregate events
-*LogsApi* | [**list_logs**](LogsApi.md#list_logs) | **POST** /api/v2/logs/events/search | Get a list of logs
-*LogsApi* | [**list_logs_get**](LogsApi.md#list_logs_get) | **GET** /api/v2/logs/events | Get a quick list of logs
+*LogsApi* | [**list_logs**](LogsApi.md#list_logs) | **POST** /api/v2/logs/events/search | Search logs
+*LogsApi* | [**list_logs_get**](LogsApi.md#list_logs_get) | **GET** /api/v2/logs/events | Get a list of logs
 *LogsArchivesApi* | [**add_read_role_to_archive**](LogsArchivesApi.md#add_read_role_to_archive) | **POST** /api/v2/logs/config/archives/{archive_id}/readers | Grant role to an archive
 *LogsArchivesApi* | [**create_logs_archive**](LogsArchivesApi.md#create_logs_archive) | **POST** /api/v2/logs/config/archives | Create an archive
 *LogsArchivesApi* | [**delete_logs_archive**](LogsArchivesApi.md#delete_logs_archive) | **DELETE** /api/v2/logs/config/archives/{archive_id} | Delete an archive

src/datadog_api_client/v1/api/logs_api.py

@@ -39,7 +39,7 @@ def __list_logs(
             body,
             **kwargs
         ):
-            """Get a list of logs  # noqa: E501
+            """Search logs  # noqa: E501
 
             List endpoint returns logs that match a log search query. [Results are paginated][1].  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives  # noqa: E501
             This method makes a synchronous HTTP request by default. To make an

src/datadog_api_client/v1/openapi.yaml

@@ -13056,7 +13056,7 @@ paths:
               schema:
                 $ref: '#/components/schemas/APIErrorResponse'
           description: Authentication error
-      summary: Get a list of logs
+      summary: Search logs
       tags:
       - Logs
       x-codegen-request-body-name: body

src/datadog_api_client/v2/api/logs_api.py

@@ -161,9 +161,9 @@ def __list_logs(
             self,
             **kwargs
         ):
-            """Get a list of logs  # noqa: E501
+            """Search logs  # noqa: E501
 
-            List endpoint returns logs that match a log search query. [Results are paginated][1].  Both this endpoint and the GET endpoint can be used interchangeably when listing logs.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives  # noqa: E501
+            List endpoint returns logs that match a log search query. [Results are paginated][1].  Use this endpoint to build complex logs filtering and search.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives  # noqa: E501
             This method makes a synchronous HTTP request by default. To make an
             asynchronous HTTP request, please pass async_req=True
 
@@ -276,9 +276,9 @@ def __list_logs_get(
             self,
             **kwargs
         ):
-            """Get a quick list of logs  # noqa: E501
+            """Get a list of logs  # noqa: E501
 
-            List endpoint returns logs that match a log search query. [Results are paginated][1].  Both this endpoint and the POST endpoint can be used interchangeably when listing logs.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives  # noqa: E501
+            List endpoint returns logs that match a log search query. [Results are paginated][1].  Use this endpoint to see your latest logs.  **If you are considering archiving logs for your organization, consider use of the Datadog archive capabilities instead of the log list API. See [Datadog Logs Archive documentation][2].**  [1]: /logs/guide/collect-multiple-logs-with-pagination [2]: https://docs.datadoghq.com/logs/archives  # noqa: E501
             This method makes a synchronous HTTP request by default. To make an
             asynchronous HTTP request, please pass async_req=True
 

src/datadog_api_client/v2/openapi.yaml

@@ -5742,10 +5742,7 @@ paths:
         [Results are paginated][1].
 
 
-        Both this endpoint and the POST endpoint can be used interchangeably when
-        listing
-
-        logs.
+        Use this endpoint to see your latest logs.
 
 
         **If you are considering archiving logs for your organization,
@@ -5827,7 +5824,7 @@ paths:
           $ref: '#/components/responses/BadRequestResponse'
         '403':
           $ref: '#/components/responses/NotAuthorizedResponse'
-      summary: Get a quick list of logs
+      summary: Get a list of logs
       tags:
       - Logs
       x-undo:
@@ -5842,9 +5839,7 @@ paths:
         [Results are paginated][1].
 
 
-        Both this endpoint and the GET endpoint can be used interchangeably when listing
-
-        logs.
+        Use this endpoint to build complex logs filtering and search.
 
 
         **If you are considering archiving logs for your organization,
@@ -5875,7 +5870,7 @@ paths:
           $ref: '#/components/responses/BadRequestResponse'
         '403':
           $ref: '#/components/responses/NotAuthorizedResponse'
-      summary: Get a list of logs
+      summary: Search logs
       tags:
       - Logs
       x-codegen-request-body-name: body

tests/v1/features/logs.feature

@@ -23,11 +23,11 @@ Feature: Logs
     And body {}
 
   @generated @skip
-  Scenario: Get a list of logs returns "Bad Request" response
+  Scenario: Search logs returns "Bad Request" response
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip
-  Scenario: Get a list of logs returns "OK" response
+  Scenario: Search logs returns "OK" response
     When the request is sent
     Then the response status is 200 OK

tests/v2/features/logs.feature

@@ -35,9 +35,8 @@ Feature: Logs
 
   @generated @skip
   Scenario: Get a list of logs returns "Bad Request" response
-    Given operation "ListLogs" enabled
-    And new "ListLogs" request
-    And body {}
+    Given operation "ListLogsGet" enabled
+    And new "ListLogsGet" request
     When the request is sent
     Then the response status is 400 Bad Request
 
@@ -48,13 +47,6 @@ Feature: Logs
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip
-  Scenario: Get a quick list of logs returns "Bad Request" response
-    Given operation "ListLogsGet" enabled
-    And new "ListLogsGet" request
-    When the request is sent
-    Then the response status is 400 Bad Request
-
   Scenario: Get a quick list of logs returns "OK" response
     Given operation "ListLogsGet" enabled
     And new "ListLogsGet" request
@@ -65,3 +57,19 @@ Feature: Logs
     And request contains "page[limit]" parameter with value 5
     When the request is sent
     Then the response status is 200 OK
+
+  @generated @skip
+  Scenario: Search logs returns "Bad Request" response
+    Given operation "ListLogs" enabled
+    And new "ListLogs" request
+    And body {}
+    When the request is sent
+    Then the response status is 400 Bad Request
+
+  @generated @skip
+  Scenario: Search logs returns "OK" response
+    Given operation "ListLogs" enabled
+    And new "ListLogs" request
+    And body {}
+    When the request is sent
+    Then the response status is 200 OK