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

Get Repository

GET
/registry/v1/workspaces/{workspace}/engines/{engine}/repositories/{id}
 
curl --request GET \
  --url https://example.com/registry/v1/workspaces/example/engines/example/repositories/example

Returns a repository by unique ID. Use - to look it up regardless of provider.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
workspace
required
string

The workspace the repository belongs to.

engine
required
string

The provider: qibdo, or - to look up across all providers.

id
required
string

The unique identifier of the repository to retrieve.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

A repository is a workspace-scoped, named collection of artifacts (e.g. nginx, ci/web-app). It is the only first-class registry resource: it carries visibility, format metadata, and is the parent scope for artifacts, deployment locks, retention policies, and scan policies. Repositories can be provisioned across different providers; the provider a repository lives on is reported by the read-only engine field.

object
id

The unique identifier of the repository.

stringOutput only
workspace_id

The workspace this repository belongs to.

stringOutput only
name
required

The repository name — a slash-capable OCI path (e.g. nginx, ci/web-app). Each slash-separated segment is a DNS-label-style token; the whole name is unique within the workspace and must not itself be a UUID. Slashes are carried in a single URL-encoded path segment on the wire (never a multi-segment wildcard).

string
description

An optional human-readable description of the repository.

string
visibility

Repository visibility. Defaults to PRIVATE — the workspace is the isolation boundary.

string format: enum
Allowed values: VISIBILITY_UNSPECIFIED VISIBILITY_PRIVATE VISIBILITY_PUBLIC
format

The artifact format stored in this repository. Defaults to DOCKER. Set at creation time, not updatable.

string format: enum Output only
Allowed values: REPOSITORY_FORMAT_UNSPECIFIED REPOSITORY_FORMAT_DOCKER REPOSITORY_FORMAT_HELM REPOSITORY_FORMAT_OCI
origin

How the repository came to exist: CREATED via the API, or DISCOVERED when an image was pushed to an unregistered name. Informational only — the two are indistinguishable to consumers once the repository exists.

string format: enum Output only
Allowed values: REPOSITORY_ORIGIN_UNSPECIFIED REPOSITORY_ORIGIN_CREATED REPOSITORY_ORIGIN_DISCOVERED
engine

The provider this repository is provisioned on.

string format: enum Output only
Allowed values: ENGINE_UNSPECIFIED ENGINE_QIBDO
create_time

Timestamp when the repository was created.

string format: date-time Output only
update_time

Timestamp when the repository was last updated.

string format: date-time Output only
qibdo

Attributes specific to a Qibdo-managed repository.

object
immutable_tags

Whether tag immutability is enforced on this repository — the registry refuses to overwrite an existing tag on push. Kept provider-specific rather than shared at the top level.

boolean
Example 
{
  "visibility": "VISIBILITY_UNSPECIFIED",
  "format": "REPOSITORY_FORMAT_UNSPECIFIED",
  "origin": "REPOSITORY_ORIGIN_UNSPECIFIED",
  "engine": "ENGINE_UNSPECIFIED"
}

default

Section titled “default ”

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"
    }
  ]
}