luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

VAULT-7707 Add docs around making mass amounts of lease count quotas via automation (#16950) 

* VAULT-7707 Add docs around making mass amounts of lease count quotas via automation

* VAULT-7707 Changelog

* VAULT-7707 add word

* VAULT-7707 Update some small wordings

* VAULT-7707 use a real em dash
This commit is contained in:
Violet Hynes 2022-08-31 11:50:01 -04:00 committed by GitHub
parent 1997fbb73f
commit 2fb4ed211d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
changelog/16950.txt Normal file
View File

@ -0,0 +1,3 @@
```release-note:improvement
website/docs: Add documentation around the expensiveness of making lots of lease count quotas in a short period
```

8
website/content/api-docs/system/lease-count-quotas.mdx
View File

@ -17,6 +17,14 @@ A lease count quota must include a `max_leases` value with an optional `path`
that can either be a namespace or mount, and can optionally include a path suffix following
the mount to restrict more specific API paths.
Upon creating a lease count quota, it will be populated with the current count of leases from this path. If there are
more leases present than the specified `max_leases`, this will cause the lease count to go over the specified
`max_leases`.
The initial population process can cause a lot of work for Vault - and while creating one lease count quota
is always fine, if you're planning to create — for example — thousands of lease count quotas for paths with
millions of leases in an automated way, it is recommended to space out the creation requests.
| Method | Path |
| :----- | :------------------------------ |
| `POST` | `/sys/quotas/lease-count/:name` |