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:
parent
1997fbb73f
commit
2fb4ed211d
|
@ -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
|
||||||
|
```
|
|
@ -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
|
that can either be a namespace or mount, and can optionally include a path suffix following
|
||||||
the mount to restrict more specific API paths.
|
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 |
|
| Method | Path |
|
||||||
| :----- | :------------------------------ |
|
| :----- | :------------------------------ |
|
||||||
| `POST` | `/sys/quotas/lease-count/:name` |
|
| `POST` | `/sys/quotas/lease-count/:name` |
|
||||||
|
|
Loading…
Reference in New Issue