From 14ee187c467b2fe560e05e3d3eb3e8f388c58c70 Mon Sep 17 00:00:00 2001
From: lcawl <lcawley@elastic.co>
Date: Fri, 31 May 2024 11:48:37 -0700
Subject: [PATCH] Remove asyn parameter from intake_v2_events.yaml

---
 docs/spec/openapi/bundled.json                | 10 ----------
 docs/spec/openapi/bundled.yaml                |  7 -------
 docs/spec/openapi/paths/intake_v2_events.yaml | 14 --------------
 3 files changed, 31 deletions(-)

diff --git a/docs/spec/openapi/bundled.json b/docs/spec/openapi/bundled.json
index 2a75bedf90a..db24a1f41ab 100644
--- a/docs/spec/openapi/bundled.json
+++ b/docs/spec/openapi/bundled.json
@@ -231,16 +231,6 @@
         "tags": [
           "event intake"
         ],
-        "parameters": [
-          {
-            "in": "query",
-            "name": "async",
-            "description": "Indicates whether to use asynchronous processing, which is supported by APM Server in 8.5.0 and later. NOTE: Since asynchronous processing defers some of the event processing to the background and takes place after the client has closed the request, some errors can't be communicated back to the client and are logged by the APM Server. Furthermore, asynchronous processing requests will only be scheduled if the APM Server can service the incoming request; requests that cannot be serviced will receive an internal error 503 \"queue is full\" error.\n",
-            "schema": {
-              "type": "boolean"
-            }
-          }
-        ],
         "requestBody": {
           "content": {
             "application/ndjson": {
diff --git a/docs/spec/openapi/bundled.yaml b/docs/spec/openapi/bundled.yaml
index 3a00bfc4547..80842a9740e 100644
--- a/docs/spec/openapi/bundled.yaml
+++ b/docs/spec/openapi/bundled.yaml
@@ -161,13 +161,6 @@ paths:
       operationId: postEventIntake
       tags:
         - event intake
-      parameters:
-        - in: query
-          name: async
-          description: |
-            Indicates whether to use asynchronous processing, which is supported by APM Server in 8.5.0 and later. NOTE: Since asynchronous processing defers some of the event processing to the background and takes place after the client has closed the request, some errors can't be communicated back to the client and are logged by the APM Server. Furthermore, asynchronous processing requests will only be scheduled if the APM Server can service the incoming request; requests that cannot be serviced will receive an internal error 503 "queue is full" error.
-          schema:
-            type: boolean
       requestBody:
         content:
           application/ndjson:
diff --git a/docs/spec/openapi/paths/intake_v2_events.yaml b/docs/spec/openapi/paths/intake_v2_events.yaml
index ab44382ba72..e9da3077ea2 100644
--- a/docs/spec/openapi/paths/intake_v2_events.yaml
+++ b/docs/spec/openapi/paths/intake_v2_events.yaml
@@ -17,20 +17,6 @@ post:
   operationId: postEventIntake
   tags:
     - event intake
-  parameters:
-    - in: query
-      name: async
-      description: >
-        Indicates whether to use asynchronous processing, which is supported by
-        APM Server in 8.5.0 and later. NOTE: Since asynchronous processing
-        defers some of the event processing to the background and takes place
-        after the client has closed the request, some errors can't be
-        communicated back to the client and are logged by the APM Server.
-        Furthermore, asynchronous processing requests will only be scheduled if
-        the APM Server can service the incoming request; requests that cannot be
-        serviced will receive an internal error 503 "queue is full" error.
-      schema:
-        type: boolean
   requestBody:
     content:
       application/ndjson: