Get Cross Namespace Grant

GET

/registry/v1/workspaces/{workspace}/namespaces/{namespace}/cross-namespace-grants/{id}

curl --request GET \
  --url https://example.com/registry/v1/workspaces/example/namespaces/example/cross-namespace-grants/example

Returns a cross-namespace grant by unique ID under the parent (workspace, source namespace).

Parameters

Path Parameters

workspace

required

string

namespace

required

string

id

required

string

Responses

200

OK

Media type application/json

object

id

stringOutput only

source_namespace_id

required

string

target_namespace_id

required

string

actions

required

Array<string>

Allowed values: REGISTRY_ACTION_UNSPECIFIED REGISTRY_ACTION_PULL REGISTRY_ACTION_PUSH REGISTRY_ACTION_DELETE REGISTRY_ACTION_ADMIN

expires_at

string format: date-time

created

string format: date-time Output only

updated

string format: date-time Output only

tag_pattern

Optional Registry-specific tag limiter constraining which image tags the grant covers (e.g. “release-*”). Empty means the grant is unrestricted.

string

Example

{
  "actions": [
    "REGISTRY_ACTION_UNSPECIFIED"
  ]
}

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