add request heading line to response examples

Author: miguelgrinberg

specification/_global/bulk/examples/response/BulkResponseExample2.yaml

@@ -1,4 +1,5 @@
 summary: Failed actions
+method_request: POST /_bulk
 description: >
   If you run `POST /_bulk` with operations that update non-existent documents, the operations cannot complete successfully.
   The API returns a response with an `errors` property value `true`.

specification/_global/bulk/examples/response/BulkResponseExample3.yaml

@@ -1,4 +1,5 @@
 summary: Filter for failed operations
+method_request: POST /_bulk?filter_path=items.*.error
 description: >
   An example response from `POST /_bulk?filter_path=items.*.error`, which returns only information about failed operations.
 # type: response

specification/_global/close_point_in_time/examples/200_response/ClosePointInTimeResponseExample1.yaml

@@ -1,4 +1,5 @@
 # summary:
+method_request: DELETE /_pit
 description: A successful response from `DELETE /_pit`.
 # type: response
 # response_code: 200

specification/_global/count/examples/200_response/CountResponseExample1.yaml

@@ -1,4 +1,5 @@
 # summary:
+method_request: GET /my-index-000001/_count?q=user:kimchy
 description: A successful response from `GET /my-index-000001/_count?q=user:kimchy`.
 # type: response
 # response_code: 200

specification/_global/delete/examples/response/DeleteResponseExample1.yaml

@@ -1,4 +1,5 @@
 # summary:
+method_request: DELETE /my-index-000001/_doc/1
 description: A successful response from `DELETE /my-index-000001/_doc/1`, which deletes the JSON document 1 from the `my-index-000001` index.
 # type: response
 # response_code: ''

specification/_global/delete_by_query/examples/response/DeleteByQueryResponseExample1.yaml

@@ -1,4 +1,5 @@
 # summary:
+method_request: POST /my-index-000001/_delete_by_query
 description: A successful response from `POST /my-index-000001/_delete_by_query`.
 # type: response
 # response_code:

specification/_global/explain/examples/response/ExplainResponseExample1.yaml

@@ -1,4 +1,5 @@
 # summary:
+method_request: GET /my-index-000001/_explain/0
 description: A successful response from `GET /my-index-000001/_explain/0`.
 # type: response
 # response_code: 200

specification/_global/field_caps/examples/request/FieldCapabilitiesRequestExample1.yaml

@@ -1,5 +1,5 @@
 # summary:
-method_request: "POST my-index-*/_field_caps?fields=rating"
+method_request: 'POST my-index-*/_field_caps?fields=rating'
 description: >
   Run `POST my-index-*/_field_caps?fields=rating` to get field capabilities and filter indices with a query.
   Indices that rewrite the provided filter to `match_none` on every shard will be filtered from the response.

specification/_global/field_caps/examples/response/FieldCapabilitiesResponseExample1.yaml

@@ -1,5 +1,6 @@
 summary: Get two fields
 # type: "response"
+method_request: GET _field_caps?fields=rating,title
 description: >
   A successful response from `GET _field_caps?fields=rating,title`.
   The field `rating` is defined as a long in `index1` and `index2` and as a `keyword` in `index3` and `index4`.

specification/_global/field_caps/examples/response/FieldCapabilitiesResponseExample2.yaml

@@ -1,5 +1,6 @@
 summary: Get unmapped fields
 # type: "response"
+method_request: GET _field_caps?fields=rating,title&include_unmapped
 description: >
   A successful response from `GET _field_caps?fields=rating,title&include_unmapped`.
   The response contains an entry for each field that is present in some indices but not all.