Update example for GetEstimatedCostByOrg (#1226)

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.4",
-            "regenerated": "2022-11-02 20:10:39.169455",
-            "spec_repo_commit": "7c5579df"
+            "regenerated": "2022-11-04 18:42:27.825188",
+            "spec_repo_commit": "af3f11fc"
         },
         "v2": {
             "apigentools_version": "1.6.4",
-            "regenerated": "2022-11-02 20:10:39.181527",
-            "spec_repo_commit": "7c5579df"
+            "regenerated": "2022-11-04 18:42:27.839660",
+            "spec_repo_commit": "af3f11fc"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -16461,7 +16461,9 @@ paths:
     get:
       description: 'Get estimated cost across multi-org and single root-org accounts.
 
-        Estimated cost data is only available for the current month and previous month.
+        Estimated cost data is only available for the current month and previous month
+
+        and is delayed by up to 72 hours from when it was incurred.
 
         To access historical costs prior to this, use the `/historical_cost` endpoint.'
       operationId: GetEstimatedCostByOrg

examples/v2/usage-metering/GetEstimatedCostByOrg_2734954020.py

@@ -3,7 +3,6 @@
 """
 
 from datetime import datetime
-from dateutil.relativedelta import relativedelta
 from datadog_api_client import ApiClient, Configuration
 from datadog_api_client.v2.api.usage_metering_api import UsageMeteringApi
 
@@ -12,7 +11,7 @@
     api_instance = UsageMeteringApi(api_client)
     response = api_instance.get_estimated_cost_by_org(
         view="sub-org",
-        start_month=(datetime.now() + relativedelta(days=-5)),
+        start_month=datetime.now(),
     )
 
     print(response)

examples/v2/usage-metering/GetEstimatedCostByOrg_3186693804.py

@@ -340,7 +340,8 @@ def get_estimated_cost_by_org(
         """Get estimated cost across your account.
 
         Get estimated cost across multi-org and single root-org accounts.
-        Estimated cost data is only available for the current month and previous month.
+        Estimated cost data is only available for the current month and previous month
+        and is delayed by up to 72 hours from when it was incurred.
         To access historical costs prior to this, use the ``/historical_cost`` endpoint.
 
         :param view: String to specify whether cost is broken down at a parent-org level or at the sub-org level. Available views are ``summary`` and ``sub-org``. Defaults to ``summary``.

src/datadog_api_client/v2/api/usage_metering_api.py

@@ -1 +1 @@
-2022-09-23T14:04:15.545Z
+2022-11-03T21:08:41.229Z

tests/v2/cassettes/test_scenarios/test_getestimatedcostbyorg_with_both_start_month_and_start_date_returns_bad_request_response.frozen

@@ -5,7 +5,7 @@ interactions:
       accept:
       - application/json;datetime-format=rfc3339
     method: GET
-    uri: https://api.datadoghq.com/api/v2/usage/estimated_cost?view=sub-org&start_month=2022-09-20T14%3A04%3A15.545Z&start_date=2022-09-20T14%3A04%3A15.545Z
+    uri: https://api.datadoghq.com/api/v2/usage/estimated_cost?view=sub-org&start_month=2022-11-03T21%3A08%3A41.229Z&start_date=2022-10-31T21%3A08%3A41.229Z
   response:
     body:
       string: '{"errors":["API called with non-parent org keys. Data is only available

tests/v2/cassettes/test_scenarios/test_getestimatedcostbyorg_with_both_start_month_and_start_date_returns_bad_request_response.yaml

@@ -0,0 +1 @@
+2022-11-04T18:40:14.021Z

tests/v2/cassettes/test_scenarios/test_getestimatedcostbyorg_with_start_month_returns_ok_response.frozen

@@ -0,0 +1,20 @@
+interactions:
+- request:
+    body: null
+    headers:
+      accept:
+      - application/json;datetime-format=rfc3339
+    method: GET
+    uri: https://api.datadoghq.com/api/v2/usage/estimated_cost?view=sub-org&start_month=2022-11-04T18%3A40%3A14.021Z
+  response:
+    body:
+      string: '{"data":[]}
+
+        '
+    headers:
+      content-type:
+      - application/json
+    status:
+      code: 200
+      message: OK
+version: 1

tests/v2/cassettes/test_scenarios/test_getestimatedcostbyorg_with_start_month_returns_ok_response.yaml

@@ -166,23 +166,15 @@ Feature: Usage Metering
   Scenario: GetEstimatedCostByOrg with both start_month and start_date returns "Bad Request" response
     Given new "GetEstimatedCostByOrg" request
     And request contains "view" parameter with value "sub-org"
-    And request contains "start_month" parameter with value "{{ timeISO('now - 3d') }}"
+    And request contains "start_month" parameter with value "{{ timeISO('now') }}"
     And request contains "start_date" parameter with value "{{ timeISO('now - 3d') }}"
     When the request is sent
     Then the response status is 400 Bad Request
 
   @replay-only @team:DataDog/red-zone-revenue-query
-  Scenario: GetEstimatedCostByOrg with start_date returns "OK" response
-    Given new "GetEstimatedCostByOrg" request
-    And request contains "view" parameter with value "sub-org"
-    And request contains "start_date" parameter with value "{{ timeISO('now - 5d') }}"
-    When the request is sent
-    Then the response status is 200 OK
-
-  @skip @team:DataDog/red-zone-revenue-query
   Scenario: GetEstimatedCostByOrg with start_month returns "OK" response
     Given new "GetEstimatedCostByOrg" request
     And request contains "view" parameter with value "sub-org"
-    And request contains "start_month" parameter with value "{{ timeISO('now - 5d') }}"
+    And request contains "start_month" parameter with value "{{ timeISO('now') }}"
     When the request is sent
     Then the response status is 200 OK