Regenerate client from commit dafec27 of spec repo (#324)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.4.1.dev6",
-            "regenerated": "2021-03-18 12:48:16.331233",
-            "spec_repo_commit": "f22ef72"
+            "regenerated": "2021-03-18 15:15:33.427751",
+            "spec_repo_commit": "dafec27"
         },
         "v2": {
             "apigentools_version": "1.4.1.dev6",
-            "regenerated": "2021-03-18 12:48:52.527816",
-            "spec_repo_commit": "f22ef72"
+            "regenerated": "2021-03-18 15:16:11.021987",
+            "spec_repo_commit": "dafec27"
         }
     }
 }

src/datadog_api_client/v1/openapi.yaml

@@ -5395,6 +5395,8 @@ components:
         format: double
         type: number
       description: A mapping of threshold `timeframe` to the remaining error budget.
+      example:
+        7d: 100.0
       type: object
     SLOErrorTimeframe:
       description: 'The timeframe of the threshold associated with this error
@@ -5427,6 +5429,7 @@ components:
           type: integer
         message:
           description: Optional message if there are specific query issues/warnings.
+          example: ''
           type: string
         numerator:
           $ref: '#/components/schemas/SLOHistoryMetricsSeries'
@@ -5563,6 +5566,7 @@ components:
           properties:
             from_ts:
               description: The `from` timestamp in epoch seconds.
+              example: 1615323990
               format: int64
               type: integer
             group_by:
@@ -5571,6 +5575,7 @@ components:
 
 
                 This is not included in responses for `monitor` based SLOs.'
+              example: []
               items:
                 description: A grouping parameter.
                 type: string
@@ -5581,6 +5586,7 @@ components:
 
 
                 This is not included in the responses for `metric` based SLOs.'
+              example: []
               items:
                 $ref: '#/components/schemas/SLOHistorySLIData'
               type: array
@@ -5590,6 +5596,7 @@ components:
 
 
                 This is not included in the responses for `metric` based SLOs.'
+              example: []
               items:
                 $ref: '#/components/schemas/SLOHistorySLIData'
               type: array
@@ -5601,9 +5608,11 @@ components:
               additionalProperties:
                 $ref: '#/components/schemas/SLOThreshold'
               description: mapping of string timeframe to the SLO threshold.
+              example: {}
               type: object
             to_ts:
               description: The `to` timestamp in epoch seconds.
+              example: 1615928790
               format: int64
               type: integer
             type:
@@ -5637,20 +5646,28 @@ components:
         errors:
           description: A list of errors while querying the history data for the service
             level objective.
+          example: []
           items:
             $ref: '#/components/schemas/SLOHistoryResponseError'
           type: array
         group:
           description: For groups in a grouped SLO, this is the group name.
+          example: name
           type: string
         history:
           description: For `monitor` based SLOs, this includes the aggregated history
             uptime time series.
           items:
             description: Represents an array time series data.
+            example:
+            - - 1579212382
+              - 0
             items:
               description: A time series data point which is a tuple of (timestamp,
                 value).
+              example:
+              - 1579212382
+              - 0
               format: double
               type: number
             maxItems: 2
@@ -5660,14 +5677,17 @@ components:
         monitor_modified:
           description: For `monitor` based SLOs, this is the last modified timestamp
             in epoch seconds of the monitor.
+          example: 1615867200
           format: int64
           type: integer
         monitor_type:
           description: For `monitor` based SLOs, this describes the type of monitor.
+          example: string
           type: string
         name:
           description: For groups in a grouped SLO, this is the group name. For monitors
             in a multi-monitor SLO, this is the monitor name.
+          example: string
           type: string
         precision:
           additionalProperties:
@@ -5676,12 +5696,16 @@ components:
             type: number
           description: A mapping of threshold `timeframe` to number of accurate decimals,
             regardless of the from && to timestamp.
+          example:
+            30d: 1
+            7d: 2
           type: object
         preview:
           description: 'For `monitor` based SLOs, when `true` this indicates that
             a replay is in progress to give an accurate uptime
 
             calculation.'
+          example: true
           type: boolean
         sli_value:
           description: The current SLI value of the SLO over the history window.
@@ -5691,11 +5715,13 @@ components:
         span_precision:
           description: The amount of decimal places the SLI value is accurate to for
             the given from `&&` to timestamp.
+          example: 2
           format: double
           type: number
         uptime:
           deprecated: true
           description: Use `sli_value` instead.
+          example: 99.99
           format: double
           type: number
       type: object
@@ -5742,7 +5768,7 @@ components:
             corresponding
 
             timeframe.'
-          example: 0.0
+          example: 99.9
           format: double
           type: number
         target_display:
@@ -5760,6 +5786,7 @@ components:
           $ref: '#/components/schemas/SLOTimeframe'
         warning:
           description: The warning value for the service level objective.
+          example: 90.0
           format: double
           type: number
         warning_display:
@@ -5772,6 +5799,7 @@ components:
             Included in service level objective responses if a warning target exists.
 
             Ignored in create/update requests.'
+          example: '90.0'
           type: string
       required:
       - timeframe
@@ -5793,6 +5821,7 @@ components:
       enum:
       - metric
       - monitor
+      example: metric
       type: string
       x-enum-varnames:
       - METRIC