- is there a size limit up to which one can store data in the kv2 engine?
- can a size limit (per key, per path) be imposed either by policy or by tuning?
- can I monitor the size of stored values (per key, per path or per mounted engine)?
- can I restrict the upload of a value by size and or filetype?
reason for asking is that if we allow “others” to store secrets in “our” vault, how can we make sure they don’t abuse it as a “general file store” - putting their “secret” pdfs or pictures or the like into it, but only use it for passwords, ssh/gpg keys and the like.