Regenerate client from commit f486a915 of spec repo (#1097)

Co-authored-by: ci.datadog-api-spec <[email protected]>
Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-07-15 12:26:10.791241",
-            "spec_repo_commit": "d854c667"
+            "regenerated": "2022-07-18 17:54:28.205368",
+            "spec_repo_commit": "f486a915"
         },
         "v2": {
             "apigentools_version": "1.6.2",
-            "regenerated": "2022-07-15 12:26:10.807992",
-            "spec_repo_commit": "d854c667"
+            "regenerated": "2022-07-18 17:54:28.232847",
+            "spec_repo_commit": "f486a915"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -27461,9 +27461,6 @@ paths:
       x-menu-order: 30
       x-undo:
         type: safe
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/usage/incident-management:
     get:
       description: Get hourly usage for incident management.
@@ -27989,9 +27986,6 @@ paths:
       x-menu-order: 31
       x-undo:
         type: safe
-      x-unstable: '**Note**: This endpoint is in public beta.
-
-        If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).'
   /api/v1/usage/network_flows:
     get:
       description: Get hourly usage for network flows.

examples/v1/usage-metering/GetHourlyUsageAttribution.py

@@ -9,7 +9,6 @@
 from datadog_api_client.v1.model.hourly_usage_attribution_usage_type import HourlyUsageAttributionUsageType
 
 configuration = Configuration()
-configuration.unstable_operations["get_hourly_usage_attribution"] = True
 with ApiClient(configuration) as api_client:
     api_instance = UsageMeteringApi(api_client)
     response = api_instance.get_hourly_usage_attribution(

examples/v1/usage-metering/GetMonthlyUsageAttribution.py

@@ -11,7 +11,6 @@
 )
 
 configuration = Configuration()
-configuration.unstable_operations["get_monthly_usage_attribution"] = True
 with ApiClient(configuration) as api_client:
     api_instance = UsageMeteringApi(api_client)
     response = api_instance.get_monthly_usage_attribution(

src/datadog_api_client/configuration.py

@@ -222,9 +222,7 @@ def __init__(
         self.unstable_operations = _UnstableOperations(
             {
                 "v1.get_daily_custom_reports": False,
-                "v1.get_hourly_usage_attribution": False,
                 "v1.get_monthly_custom_reports": False,
-                "v1.get_monthly_usage_attribution": False,
                 "v1.get_specified_daily_custom_reports": False,
                 "v1.get_specified_monthly_custom_reports": False,
                 "v1.get_usage_attribution": False,

tests/v1/features/usage_metering.feature

@@ -57,17 +57,15 @@ Feature: Usage Metering
 
   @skip @team:DataDog/red-zone-revenue-query
   Scenario: Get hourly usage attribution returns "Bad Request" response
-    Given operation "GetHourlyUsageAttribution" enabled
-    And new "GetHourlyUsageAttribution" request
+    Given new "GetHourlyUsageAttribution" request
     And request contains "start_hr" parameter with value "{{ timeISO('now - 3d') }}"
     And request contains "usage_type" parameter with value "not_a_product"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/red-zone-revenue-query
   Scenario: Get hourly usage attribution returns "OK" response
-    Given operation "GetHourlyUsageAttribution" enabled
-    And new "GetHourlyUsageAttribution" request
+    Given new "GetHourlyUsageAttribution" request
     And request contains "start_hr" parameter with value "{{ timeISO('now - 3d') }}"
     And request contains "usage_type" parameter with value "infra_host_usage"
     When the request is sent
@@ -507,17 +505,15 @@ Feature: Usage Metering
 
   @skip @team:DataDog/red-zone-revenue-query
   Scenario: Get monthly usage attribution returns "Bad Request" response
-    Given operation "GetMonthlyUsageAttribution" enabled
-    And new "GetMonthlyUsageAttribution" request
+    Given new "GetMonthlyUsageAttribution" request
     And request contains "start_month" parameter with value "{{ timeISO('now - 3d') }}"
     And request contains "fields" parameter with value "not_a_product"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @team:DataDog/red-zone-revenue-query
   Scenario: Get monthly usage attribution returns "OK" response
-    Given operation "GetMonthlyUsageAttribution" enabled
-    And new "GetMonthlyUsageAttribution" request
+    Given new "GetMonthlyUsageAttribution" request
     And request contains "start_month" parameter with value "{{ timeISO('now - 3d') }}"
     And request contains "fields" parameter with value "infra_host_usage"
     When the request is sent