List Quota Limits
const url = 'https://example.com/registry/v1/workspaces/example/quota-limits';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/registry/v1/workspaces/example/quota-limitsReturns a paginated list of the workspace’s quota limit overrides.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the workspace to list overrides for
Query Parameters
Section titled “Query Parameters ”The maximum number of quota limits to return. The service may return fewer than this value. If unspecified, at most 20 limits will be returned. The maximum value is 100; values above 100 will be coerced to 100.
A page token, received from a previous ListQuotaLimits call. Provide this to
retrieve the subsequent page. When paginating, all other parameters must match the
call that provided the page token.
AIP-160 filter expression. Filterable fields: container_id, container_type, create_time, effective_limit, id, quota_definition_id, update_time.
AIP-132 order_by expression. Sortable fields: container_type, create_time, effective_limit, update_time.
AIP-158 offset mode: number of resources to skip from the start of the filtered, sorted set. Use EITHER skip (offset paging) OR page_token (cursor paging) — never both in the same request. Supplying both is an invalid request. Default 0 (no skip).
Responses
Section titled “ Responses ”OK
ListQuotaLimitsResponse
Response message for ListQuotaLimits.
object
The list of quota limits.
QuotaLimit — an override of a quota definition’s default limit for one workspace.
Resolution is override, else the definition's default_limit; deleting the override
restores the default.
The workspace an override applies to is taken from the request path, never from this
message: container_id and container_type are stamped by the server. A caller can
therefore not address one workspace in the path and write an override for another.
object
Unique identifier for this quota limit.
The quota definition this limit overrides.
The scoped resource this limit applies to. Stamped from the request path.
The taxonomy scope type. Always WORKSPACE for registry quotas. Stamped by the server.
Key-value dimension overrides. Empty map means global/unscoped. Keys must be from the parent definition’s dimension_keys list.
object
The overridden limit for this container and dimensions, in the definition’s unit.
Created Timestamp
When this quota limit was created.
Updated Timestamp
When this quota limit was last updated.
A token, which can be sent as page_token to retrieve the next page.
If this field is empty, there are no subsequent pages.
Exact count of resources matching the request’s filter and scope (both pagination modes).
Example
{ "quota_limits": [ { "container_type": "QUOTA_CONTAINER_TYPE_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}