Document support for BYDAY in SLO corrections (#2357)

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-01-18 22:51:58.199195",
-            "spec_repo_commit": "4d921fb1"
+            "regenerated": "2024-01-19 00:00:01.299640",
+            "spec_repo_commit": "7dba000a"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-01-18 22:51:58.221645",
-            "spec_repo_commit": "4d921fb1"
+            "regenerated": "2024-01-19 00:00:01.331313",
+            "spec_repo_commit": "7dba000a"
         }
     }
 }

.generator/schemas/v1/openapi.yaml

@@ -10074,7 +10074,7 @@ components:
           description: 'The recurrence rules as defined in the iCalendar RFC 5545.
             The supported rules for SLO corrections
 
-            are `FREQ`, `INTERVAL`, `COUNT` and `UNTIL`.'
+            are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.'
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           type: string
         slo_id:
@@ -10151,7 +10151,7 @@ components:
           description: 'The recurrence rules as defined in the iCalendar RFC 5545.
             The supported rules for SLO corrections
 
-            are `FREQ`, `INTERVAL`, `COUNT`, and `UNTIL`.'
+            are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.'
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           nullable: true
           type: string
@@ -10227,7 +10227,7 @@ components:
           description: 'The recurrence rules as defined in the iCalendar RFC 5545.
             The supported rules for SLO corrections
 
-            are `FREQ`, `INTERVAL`, `COUNT`, and `UNTIL`.'
+            are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.'
           example: FREQ=DAILY;INTERVAL=10;COUNT=5
           type: string
         start:

api/datadogV1/model_slo_correction_create_request_attributes.go

@@ -21,7 +21,7 @@ type SLOCorrectionCreateRequestAttributes struct {
 	// Ending time of the correction in epoch seconds.
 	End *int64 `json:"end,omitempty"`
 	// The recurrence rules as defined in the iCalendar RFC 5545. The supported rules for SLO corrections
-	// are `FREQ`, `INTERVAL`, `COUNT` and `UNTIL`.
+	// are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.
 	Rrule *string `json:"rrule,omitempty"`
 	// ID of the SLO that this correction applies to.
 	SloId string `json:"slo_id"`

api/datadogV1/model_slo_correction_response_attributes.go

@@ -27,7 +27,7 @@ type SLOCorrectionResponseAttributes struct {
 	// Modifier of the object.
 	Modifier NullableSLOCorrectionResponseAttributesModifier `json:"modifier,omitempty"`
 	// The recurrence rules as defined in the iCalendar RFC 5545. The supported rules for SLO corrections
-	// are `FREQ`, `INTERVAL`, `COUNT`, and `UNTIL`.
+	// are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.
 	Rrule datadog.NullableString `json:"rrule,omitempty"`
 	// ID of the SLO that this correction applies to.
 	SloId *string `json:"slo_id,omitempty"`

api/datadogV1/model_slo_correction_update_request_attributes.go

@@ -19,7 +19,7 @@ type SLOCorrectionUpdateRequestAttributes struct {
 	// Ending time of the correction in epoch seconds.
 	End *int64 `json:"end,omitempty"`
 	// The recurrence rules as defined in the iCalendar RFC 5545. The supported rules for SLO corrections
-	// are `FREQ`, `INTERVAL`, `COUNT`, and `UNTIL`.
+	// are `FREQ`, `INTERVAL`, `COUNT`, `UNTIL` and `BYDAY`.
 	Rrule *string `json:"rrule,omitempty"`
 	// Starting time of the correction in epoch seconds.
 	Start *int64 `json:"start,omitempty"`