upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-12 18:37:18 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Fix typo in Consul ref (#25026)

Browse source 
* Fix typo in Consul ref

* Two more typos fixed

---------

Co-authored-by: ml4 <ml4@psy.industries>
This commit is contained in:
Mark Lewis 2024-01-24 20:42:27 +00:00 committed by GitHub
parent e735f12fd4
commit 3ab045a170
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/content/partials/storage-entry-size.mdx
View file

@ -2,13 +2,13 @@ The maximum size of an object written to a storage backend is determined
by that backend.
The default entry size limit for the integrated storage backend, is 1 MiB. You
can configure the allowable entry size with the `max_entry_size` paramter in
can configure the allowable entry size with the `max_entry_size` parameter in
your the [storage stanza](/vault/docs/configuration/storage/raft#max_entry_size).
Vault automatically chunks any storage entry that is larger than 512 KiB but
smaller than `max_entry_size` into smaller pieces before writing the entry to Raft.
For Vault deployments using the Consul storage backend, the default entry size
limit is 512 KiB. The default size in enforced by Consol rather than Vault. You
limit is 512 KiB. The default size is enforced by Consul rather than Vault. You
can configure the entry size limit with the
[`kv_max_value_size`](/consul/docs/agent/config/config-files#kv_max_value_size)
Consul parameter.