docs: make dispatch payload size limit unambiguous
This commit is contained in:
parent
bbfaa5e9ad
commit
2139e029ec
|
@ -1236,7 +1236,7 @@ The table below shows this endpoint's support for
|
|||
in the job file during submission). This is specified as part of the path.
|
||||
|
||||
- `Payload` `(string: "")` - Specifies a base64 encoded string containing the
|
||||
payload. This is limited to 15 KB.
|
||||
payload. This is limited to 16384 bytes (16KiB).
|
||||
|
||||
- `Meta` `(meta<string|string>: nil)` - Specifies arbitrary metadata to pass to
|
||||
the job.
|
||||
|
|
|
@ -29,7 +29,7 @@ dispatched instance can be provided via stdin by using "-" for the input source
|
|||
or by specifying a path to a file. Metadata can be supplied by using the meta
|
||||
flag one or more times.
|
||||
|
||||
The payload has a **size limit of 16KiB**.
|
||||
The payload has a **size limit of 16384 bytes (16KiB)**.
|
||||
|
||||
Upon successful creation, the dispatched job ID will be printed and the
|
||||
triggered evaluation will be monitored. This can be disabled by supplying the
|
||||
|
|
Loading…
Reference in a new issue