Fix required parameters (#5704) (#5715)

(cherry picked from commit d342948)

Co-authored-by: Quentin Pradet <quentin.pradet@elastic.co>

Author: github-actions[bot]

specification/_global/delete_by_query_rethrottle/DeleteByQueryRethrottleRequest.ts

@@ -50,6 +50,6 @@ export interface Request extends RequestBase {
      * The throttle for this request in sub-requests per second.
      * To disable throttling, set it to `-1`.
      */
-    requests_per_second?: float
+    requests_per_second: float
   }
 }

specification/_global/reindex_rethrottle/ReindexRethrottleRequest.ts

@@ -58,6 +58,6 @@ export interface Request extends RequestBase {
      * The throttle for this request in sub-requests per second.
      * It can be either `-1` to turn off throttling or any decimal number like `1.7` or `12` to throttle to that level.
      */
-    requests_per_second?: float
+    requests_per_second: float
   }
 }

specification/_global/update_by_query_rethrottle/UpdateByQueryRethrottleRequest.ts

@@ -49,8 +49,7 @@ export interface Request extends RequestBase {
     /**
      * The throttle for this request in sub-requests per second.
      * To turn off throttling, set it to `-1`.
-     * @server_default -1
      */
-    requests_per_second?: float
+    requests_per_second: float
   }
 }

specification/dangling_indices/delete_dangling_index/DeleteDanglingIndexRequest.ts

@@ -48,8 +48,9 @@ export interface Request extends RequestBase {
   query_parameters: {
     /**
      * This parameter must be set to true to acknowledge that it will no longer be possible to recove data from the dangling index.
+     * @server_default false
      */
-    accept_data_loss: boolean
+    accept_data_loss?: boolean
     /**
      * @server_default 30s
      */

specification/dangling_indices/import_dangling_index/ImportDanglingIndexRequest.ts

@@ -49,8 +49,9 @@ export interface Request extends RequestBase {
     /**
      * This parameter must be set to true to import a dangling index.
      * Because Elasticsearch cannot know where the dangling index data came from or determine which shard copies are fresh and which are stale, it cannot guarantee that the imported data represents the latest state of the index when it was last in the cluster.
+     * @server_default false
      */
-    accept_data_loss: boolean
+    accept_data_loss?: boolean
     /**
      * @server_default 30s
      */