QuotaService
plany.quota.v1.QuotaService — your limits, what you are using, and asking for more.
Every account and project has limits — how many servers, how many vCPUs, how much storage — set by its plan. This service shows the limits and your usage against them, and is where you ask for a higher one.
Reading limits
| Call | What it returns |
|---|---|
ListQuotaMetrics | Every limit that exists, its unit, and whether it counts per account or per project and region. |
ListQuotaLimits | Your effective limits and current usage, for accounts/{account} or projects/{project}. Pass location for one region. |
GetQuotaLimit | One limit. |
ListQuotaOverrides | Increases that have been granted to you. |
QuotasAsking for more
Every limit can be raised. CreateQuotaIncreaseRequest takes the metric, the
limit you want — the new total, not the difference — and, optionally, why.
Ask on whatever holds the limit: the account for an account-wide limit such as
projects, the project (with a location) for a per-region one such as servers. Many
requests are granted on the spot; the rest go to a person at Plany, who decides
and tells you why. Either way you are emailed the outcome.
plany quota request --metric project.plany.cloud/projects --limit 20 \ --justification "One project per customer we host for"The request's state and decision say where it is. granted_limit can be
lower than you asked for, and decision_reason carries the sentence the person
who decided wrote. ListQuotaIncreaseRequests shows every request on an account
or project, and WithdrawQuotaIncreaseRequest cancels one still waiting.
Permissions
| Permission | Lets you |
|---|---|
quota.limits.get | Read limits, usage and overrides. |
quota.increaseRequests.create | Ask for an increase. |
quota.increaseRequests.list | See requests and their outcomes. Held by viewers too, so anyone on a project can see why a limit has or has not moved. |
A create that would go over a limit is refused with RESOURCE_EXHAUSTED and a
link to request more. See Errors.