Regenerate client from commit 2008da91 of spec repo

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-03-15 14:24:46.921309",
-            "spec_repo_commit": "95184165"
+            "regenerated": "2024-03-15 19:35:00.168567",
+            "spec_repo_commit": "2008da91"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-03-15 14:24:46.946011",
-            "spec_repo_commit": "95184165"
+            "regenerated": "2024-03-15 19:35:00.185897",
+            "spec_repo_commit": "2008da91"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -411,6 +411,13 @@ components:
       required: true
       schema:
         type: string
+    ReportID:
+      description: The ID of the report object.
+      in: path
+      name: report_id
+      required: true
+      schema:
+        type: string
     ResourceID:
       description: 'Identifier, formatted as `type:id`. Supported types: `connection`,
         `dashboard`, `notebook`, `security-rule`, `slo`.'
@@ -16487,6 +16494,92 @@ components:
       type: string
       x-enum-varnames:
       - SAML_ASSERTION_ATTRIBUTES
+    SLOReportInterval:
+      description: The interval type used for each reporting period.
+      enum:
+      - weekly
+      - monthly
+      example: weekly
+      type: string
+      x-enum-varnames:
+      - WEEKLY
+      - MONTHLY
+    SLOReportPostRequest:
+      description: SLO report Post Request.
+      properties:
+        data:
+          $ref: '#/components/schemas/SLOReportPostRequestData'
+      required:
+      - data
+      type: object
+    SLOReportPostRequestData:
+      description: SLO report Post Request data.
+      properties:
+        attributes:
+          $ref: '#/components/schemas/SloReportPostRequestAttributes'
+      required:
+      - attributes
+      type: object
+    SLOReportPostResponse:
+      description: SLO report Post Response.
+      properties:
+        data:
+          $ref: '#/components/schemas/SLOReportPostResponseData'
+      type: object
+    SLOReportPostResponseData:
+      description: SLO report Post Response data.
+      properties:
+        id:
+          description: The ID of the report object.
+          example: dc8d92aa-e0af-11ee-af21-1feeaccaa3a3
+          type: string
+        type:
+          description: The type of ID.
+          example: report_id
+          type: string
+      type: object
+    SLOReportStatus:
+      description: The completion status of the SLO report.
+      enum:
+      - IN_PROGRESS
+      - COMPLETED
+      - COMPLETED_WITH_ERRORS
+      - FAILED
+      - UNKNOWN
+      example: COMPLETED
+      type: string
+      x-enum-varnames:
+      - IN_PROGRESS
+      - COMPLETED
+      - COMPLETED_WITH_ERRORS
+      - FAILED
+      - UNKNOWN
+    SLOReportStatusGetResponse:
+      description: SLO report status Get Response.
+      properties:
+        data:
+          $ref: '#/components/schemas/SLOReportStatusGetResponseData'
+      type: object
+    SLOReportStatusGetResponseAttributes:
+      description: SLO report status Get Response attributes.
+      properties:
+        status:
+          $ref: '#/components/schemas/SLOReportStatus'
+      type: object
+    SLOReportStatusGetResponseData:
+      description: SLO report status Get Response data.
+      properties:
+        attributes:
+          $ref: '#/components/schemas/SLOReportStatusGetResponseAttributes'
+        id:
+          description: The ID of the report object.
+          example: dc8d92aa-e0af-11ee-af21-1feeaccaa3a3
+          type: string
+        type:
+          description: The type of ID.
+          example: report_id
+          type: string
+      type: object
     ScalarColumn:
       description: A single column in a scalar query response.
       oneOf:
@@ -20124,6 +20217,34 @@ components:
       - channel_name
       - redirect_url
       type: object
+    SloReportPostRequestAttributes:
+      description: Attributes for a new SLO Report.
+      properties:
+        from_ts:
+          description: The `from` timestamp for the report in epoch seconds.
+          example: 1690901870
+          format: int64
+          type: integer
+        interval:
+          $ref: '#/components/schemas/SLOReportInterval'
+        query:
+          description: The query string used to filter SLO results. Some examples
+            of queries include `service:<service-name>` and `slo-name`.
+          example: slo_type:metric
+          type: string
+        timezone:
+          description: The timezone used when generating intervals for the report.
+          example: America/New_York
+          type: string
+        to_ts:
+          description: The `to` timestamp for the report in epoch seconds.
+          example: 1706803070
+          format: int64
+          type: integer
+      required:
+      - from_ts
+      - to_ts
+      type: object
     SortDirection:
       default: desc
       description: The direction to sort by.
@@ -33589,6 +33710,143 @@ paths:
       - Incident Services
       x-codegen-request-body-name: body
       x-unstable: '**Note**: This endpoint is deprecated.'
+  /api/v2/slo/report:
+    post:
+      description: 'Create a new SLO report object. The report is generated asynchronously
+        and can
+
+        be retrieved as a CSV once completed.'
+      operationId: CreateSLOReport
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/SLOReportPostRequest'
+        description: SLO report request object.
+        required: true
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SLOReportPostResponse'
+          description: OK
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Bad Request
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ:
+        - slos_read
+      summary: Create a new SLO report
+      tags:
+      - Service Level Objectives
+      x-codegen-request-body-name: body
+      x-unstable: '**Note: This feature is in private beta. If you are interested
+        in joining,
+
+        contact [Datadog support](https://docs.datadoghq.com/help/).**'
+  /api/v2/slo/report/{report_id}/download:
+    get:
+      description: 'Download a completed SLO report. This can only be performed after
+        the report has been completed.
+
+
+        Reports are not guaranteed to exist indefinitely. It is recommended to download
+        the report as soon as it is completed.'
+      operationId: GetSLOReport
+      parameters:
+      - $ref: '#/components/parameters/ReportID'
+      responses:
+        '200':
+          content:
+            text/csv:
+              schema:
+                type: string
+          description: OK
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Not Found
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ:
+        - slos_read
+      summary: Get SLO report
+      tags:
+      - Service Level Objectives
+      x-unstable: '**Note: This feature is in private beta. If you are interested
+        in joining,
+
+        contact [Datadog support](https://docs.datadoghq.com/help/).**'
+  /api/v2/slo/report/{report_id}/status:
+    get:
+      description: Get the completion status of an SLO report object.
+      operationId: GetSLOReportStatus
+      parameters:
+      - $ref: '#/components/parameters/ReportID'
+      responses:
+        '200':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/SLOReportStatusGetResponse'
+          description: OK
+        '400':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Bad Request
+        '403':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Forbidden
+        '404':
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/APIErrorResponse'
+          description: Not Found
+        '429':
+          $ref: '#/components/responses/TooManyRequestsResponse'
+      security:
+      - apiKeyAuth: []
+        appKeyAuth: []
+      - AuthZ:
+        - slos_read
+      summary: Get SLO report status
+      tags:
+      - Service Level Objectives
+      x-unstable: '**Note: This feature is in private beta. If you are interested
+        in joining,
+
+        contact [Datadog support](https://docs.datadoghq.com/help/).**'
   /api/v2/spans/analytics/aggregate:
     post:
       description: 'The API endpoint to aggregate spans into buckets and compute metrics
@@ -35996,6 +36254,18 @@ tags:
   externalDocs:
     url: https://docs.datadoghq.com/tracing/service_catalog/
   name: Service Definition
+- description: '[Service Level Objectives](https://docs.datadoghq.com/monitors/service_level_objectives/#configuration)
+
+    (or SLOs) are a key part of the site reliability engineering toolkit.
+
+    SLOs provide a framework for defining clear targets around application performance,
+
+    which ultimately help teams provide a consistent customer experience,
+
+    balance feature development with platform stability,
+
+    and improve communication with internal and external users.'
+  name: Service Level Objectives
 - description: 'API to create, update scorecard rules and outcomes. See [Service Scorecards](https://docs.datadoghq.com/service_catalog/scorecards)
     for more information.
 

api/datadog/configuration.go

@@ -364,6 +364,9 @@ func NewConfiguration() *Configuration {
 			"v2.GetIncidentService":           false,
 			"v2.ListIncidentServices":         false,
 			"v2.UpdateIncidentService":        false,
+			"v2.CreateSLOReport":              false,
+			"v2.GetSLOReport":                 false,
+			"v2.GetSLOReportStatus":           false,
 			"v2.CreateIncidentTeam":           false,
 			"v2.DeleteIncidentTeam":           false,
 			"v2.GetIncidentTeam":              false,