Skip to content
qibdo qibdo
v1
API version
  • v1
Theme
Book a demo

Get Quota Limit

GET
/registry/v1/workspaces/{workspace}/quota-limits/{id}
curl --request GET \
--url https://example.com/registry/v1/workspaces/example/quota-limits/example

Returns a quota limit override by its unique ID.

workspace
required
string

The unique identifier of the workspace the override belongs to

id
required
string

The unique identifier of the quota limit to retrieve

OK

Media type application/json

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
id

Unique identifier for this quota limit.

stringOutput only
quota_definition_id
required

The quota definition this limit overrides.

string
container_id

The scoped resource this limit applies to. Stamped from the request path.

stringOutput only
container_type

The taxonomy scope type. Always WORKSPACE for registry quotas. Stamped by the server.

string format: enum Output only
Allowed values: QUOTA_CONTAINER_TYPE_UNSPECIFIED QUOTA_CONTAINER_TYPE_ORGANISATION QUOTA_CONTAINER_TYPE_WORKSPACE QUOTA_CONTAINER_TYPE_GROUP
dimensions

Key-value dimension overrides. Empty map means global/unscoped. Keys must be from the parent definition’s dimension_keys list.

object
key
additional properties
string
effective_limit
required

The overridden limit for this container and dimensions, in the definition’s unit.

integer format: int32
create_time

Created Timestamp

When this quota limit was created.

string format: date-time Output only
update_time

Updated Timestamp

When this quota limit was last updated.

string format: date-time Output only
Example
{
"container_type": "QUOTA_CONTAINER_TYPE_UNSPECIFIED"
}

Default error response

Media type application/json

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
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

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.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
"code": 1,
"message": "example",
"details": [
{
"@type": "example"
}
]
}