Fix references to deprecated server.maxPayloadBytes config property

This was recently renamed to `server.maxPayload`, I just updated the
docs and other references accordingly. Unrelated to the other work in
this PR besides the fact that I am mucking around in the
`src/core/server/http/http_config.ts` file.

config/kibana.yml

@@ -23,7 +23,7 @@
 #server.publicBaseUrl: ""
 
 # The maximum payload size in bytes for incoming server requests.
-#server.maxPayloadBytes: 1048576
+#server.maxPayload: 1048576
 
 # The Kibana server's name.  This is used for display purposes.
 #server.name: "your-hostname"

docs/development/core/server/kibana-plugin-core-server.routeconfigoptionsbody.maxbytes.md

@@ -6,7 +6,7 @@
 
 Limits the size of incoming payloads to the specified byte count. Allowing very large payloads may cause the server to run out of memory.
 
-Default value: The one set in the kibana.yml config file under the parameter `server.maxPayloadBytes`<!-- -->.
+Default value: The one set in the kibana.yml config file under the parameter `server.maxPayload`<!-- -->.
 
 <b>Signature:</b>
 

docs/development/core/server/kibana-plugin-core-server.routeconfigoptionsbody.md

@@ -17,7 +17,7 @@ export interface RouteConfigOptionsBody
 |  Property | Type | Description |
 |  --- | --- | --- |
 |  [accepts](./kibana-plugin-core-server.routeconfigoptionsbody.accepts.md) | <code>RouteContentType &#124; RouteContentType[] &#124; string &#124; string[]</code> | A string or an array of strings with the allowed mime types for the endpoint. Use this settings to limit the set of allowed mime types. Note that allowing additional mime types not listed above will not enable them to be parsed, and if parse is true, the request will result in an error response.<!-- -->Default value: allows parsing of the following mime types: \* application/json \* application/\*+json \* application/octet-stream \* application/x-www-form-urlencoded \* multipart/form-data \* text/\* |
-|  [maxBytes](./kibana-plugin-core-server.routeconfigoptionsbody.maxbytes.md) | <code>number</code> | Limits the size of incoming payloads to the specified byte count. Allowing very large payloads may cause the server to run out of memory.<!-- -->Default value: The one set in the kibana.yml config file under the parameter <code>server.maxPayloadBytes</code>. |
+|  [maxBytes](./kibana-plugin-core-server.routeconfigoptionsbody.maxbytes.md) | <code>number</code> | Limits the size of incoming payloads to the specified byte count. Allowing very large payloads may cause the server to run out of memory.<!-- -->Default value: The one set in the kibana.yml config file under the parameter <code>server.maxPayload</code>. |
 |  [output](./kibana-plugin-core-server.routeconfigoptionsbody.output.md) | <code>typeof validBodyOutput[number]</code> | The processed payload format. The value must be one of: \* 'data' - the incoming payload is read fully into memory. If parse is true, the payload is parsed (JSON, form-decoded, multipart) based on the 'Content-Type' header. If parse is false, a raw Buffer is returned. \* 'stream' - the incoming payload is made available via a Stream.Readable interface. If the payload is 'multipart/form-data' and parse is true, field values are presented as text while files are provided as streams. File streams from a 'multipart/form-data' upload will also have a hapi property containing the filename and headers properties. Note that payload streams for multipart payloads are a synthetic interface created on top of the entire multipart content loaded into memory. To avoid loading large multipart payloads into memory, set parse to false and handle the multipart payload in the handler using a streaming parser (e.g. pez).<!-- -->Default value: 'data', unless no validation.body is provided in the route definition. In that case the default is 'stream' to alleviate memory pressure. |
 |  [parse](./kibana-plugin-core-server.routeconfigoptionsbody.parse.md) | <code>boolean &#124; 'gunzip'</code> | Determines if the incoming payload is processed or presented raw. Available values: \* true - if the request 'Content-Type' matches the allowed mime types set by allow (for the whole payload as well as parts), the payload is converted into an object when possible. If the format is unknown, a Bad Request (400) error response is sent. Any known content encoding is decoded. \* false - the raw payload is returned unmodified. \* 'gunzip' - the raw payload is returned unmodified after any known content encoding is decoded.<!-- -->Default value: true, unless no validation.body is provided in the route definition. In that case the default is false to alleviate memory pressure. |
 

docs/maps/trouble-shooting.asciidoc

@@ -32,7 +32,7 @@ image::maps/images/inspector.png[]
   ** Ensure your geospatial field is searchable and aggregatable.
   ** If your geospatial field type does not match your Elasticsearch mapping, click the *Refresh* button to refresh the field list from Elasticsearch.
 * Index patterns with thousands of fields can exceed the default maximum payload size.
-Increase <<settings, `server.maxPayloadBytes`>> for large index patterns.
+Increase <<settings, `server.maxPayload`>> for large index patterns.
 
 [float]
 ==== Features are not displayed

docs/setup/settings.asciidoc

@@ -473,7 +473,7 @@ confident your server can hold this many objects in memory.
  | The maximum byte size of a saved objects import that the {kib} server will accept.
 This setting exists to prevent the {kib} server from runnning out of memory when handling
 a large import payload. Note that this setting overrides the more general
-<<server-maxPayloadBytes, `server.maxPayloadBytes`>> for saved object imports only.
+<<server-maxPayload, `server.maxPayload`>> for saved object imports only.
 *Default: `26214400`*
 
 |[[server-basePath]] `server.basePath:`
@@ -517,6 +517,10 @@ back end server. To allow remote users to connect, set the value to the IP addre
 the <<server-socketTimeout, `server.socketTimeout`>> counter. *Default: `"120000"`*
 
 |[[server-maxPayloadBytes]] `server.maxPayloadBytes:`
+ | deprecated:[7.13.0,"This setting will no longer be supported as of 8.0."]
+ This setting has been renamed to <<server-maxPayload,`server.maxPayload`>>.
+
+|[[server-maxPayload]] `server.maxPayload:`
  | The maximum payload size in bytes
 for incoming server requests. *Default: `1048576`*
 

src/core/server/http/router/route.ts

@@ -70,7 +70,7 @@ export interface RouteConfigOptionsBody {
   /**
    * Limits the size of incoming payloads to the specified byte count. Allowing very large payloads may cause the server to run out of memory.
    *
-   * Default value: The one set in the kibana.yml config file under the parameter `server.maxPayloadBytes`.
+   * Default value: The one set in the kibana.yml config file under the parameter `server.maxPayload`.
    */
   maxBytes?: number;
 

src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker

@@ -122,6 +122,7 @@ kibana_vars=(
     server.host
     server.keepAliveTimeout
     server.maxPayloadBytes
+    server.maxPayload
     server.name
     server.port
     server.rewriteBasePath

test/common/config.js

@@ -50,7 +50,7 @@ export default function () {
         // These are *very* important to have them pointing to staging
         '--telemetry.url=https://telemetry-staging.elastic.co/xpack/v2/send',
         '--telemetry.optInStatusUrl=https://telemetry-staging.elastic.co/opt_in_status/v2/send',
-        `--server.maxPayloadBytes=1679958`,
+        `--server.maxPayload=1679958`,
         // newsfeed mock service
         `--plugin-path=${path.join(__dirname, 'fixtures', 'plugins', 'newsfeed')}`,
         `--newsfeed.service.urlRoot=${servers.kibana.protocol}://${servers.kibana.hostname}:${servers.kibana.port}`,