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

Get Image Repository

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

Returns an image repository by unique ID.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
workspace
required
string

The unique identifier of the workspace that the namespace belongs to

namespace
required
string

The unique identifier of the parent namespace

id
required
string

The unique identifier of the image repository to retrieve

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

Format: set at creation time, not updatable. Enforced at handler level via UpdateFieldMapping.immutableFields().

object
id
stringOutput only
namespace_id
stringOutput only
name
required
string
description
string
visibility
string format: enum
Allowed values: VISIBILITY_UNSPECIFIED VISIBILITY_PRIVATE VISIBILITY_PUBLIC
immutable_tags
boolean
format
string format: enum Output only
Allowed values: REPOSITORY_FORMAT_UNSPECIFIED REPOSITORY_FORMAT_DOCKER REPOSITORY_FORMAT_HELM REPOSITORY_FORMAT_OCI
created
string format: date-time Output only
updated
string format: date-time Output only
Example 
{
  "visibility": "VISIBILITY_UNSPECIFIED",
  "format": "REPOSITORY_FORMAT_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"
    }
  ]
}