Create Cross-Workspace Pull Grant
const url = 'https://example.com/registry/v1/workspaces/example/engines/example/pull-grants';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"target_workspace_id":"example","repository_id":"example","repo_name_pattern":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/registry/v1/workspaces/example/engines/example/pull-grants \ --header 'Content-Type: application/json' \ --data '{ "target_workspace_id": "example", "repository_id": "example", "repo_name_pattern": "example" }'Grants a target workspace read-only pull access to a source repository (or a glob of source
repositories). The {workspace} path segment is the source workspace being shared out.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The source workspace whose repositories are shared out.
Request Body required
Section titled “Request Body required ”A cross-workspace pull grant lets principals of a TARGET workspace pull (read-only) from a SOURCE workspace’s registry — either one specific source repository or a glob of source repository names. Sharing out a source workspace’s repositories is the source owner’s act, so a grant is created under the source workspace path. Grants are pull-only by construction: there is no action field and no push is ever conferred.
object
The provider the grant applies to.
The workspace whose repositories are shared. Stamped from the request path — a caller cannot address one workspace in the path and grant out another’s repositories.
The workspace whose principals gain pull access to the source’s repositories.
A specific source repository to share. Exactly one of repository_id or repo_name_pattern
must be set (enforced by the domain model). Present when the grant targets a single repository.
A glob over source repository names (doublestar syntax, e.g. web/**). Exactly one of
repository_id or repo_name_pattern must be set. Present when the grant targets a pattern.
Created Timestamp
When this grant was created.
Updated Timestamp
When this grant was last updated.
Responses
Section titled “ Responses ”OK
Registry Operation
An acknowledgment of a mutation request, carrying tracking metadata, errors, and warnings. Follows GCP’s Operations pattern (AIP-151).
object
Operation ID
Unique identifier for this operation.
Resource ID
The ID of the resource affected by this operation. May be empty for async operations where the resource does not yet exist.
Resource Type
The type of resource (e.g., “com.qibdo.cloud.registry:repository”).
Operation Type
The kind of mutation that was requested.
Status
Current lifecycle state of the operation.
Insert Time
When the operation was first created.
Start Time
When the operation started executing.
End Time
When the operation completed (either successfully or with errors).
Errors
Business rule errors encountered during the operation.
Operation Error
A structured error returned inside an operation when a business rule fails.
object
Error Code
Numeric identifier following the S_SSS_EEE convention.
Description
Human-readable explanation of the error.
Reason
Machine-readable error identifier in UPPER_SNAKE form — the same dispatch
key google.rpc.ErrorInfo.reason carries on the synchronous error plane.
Warnings
Non-fatal notices about the operation.
Operation Warning
A non-fatal notice attached to an operation.
object
Warning Code
Numeric identifier following the S_SSS_EEE convention.
Description
Human-readable explanation of the warning.
Progress
Percentage of completion (0-100).
Scope Type
The category of scope the operation ran in or was triggered from. REGISTRY_SCOPE_TYPE_UNSPECIFIED when the operation is not scoped.
Scope ID
The resource this operation was scoped to — for example, when scope_type is REGISTRY_SCOPE_TYPE_WORKSPACE this is the workspace id. Empty for REGISTRY_SCOPE_TYPE_PLATFORM, which has no scoped resource, and when unscoped.
Principal ID
Who performed or triggered the operation, whether a person or a machine account. Always populated: platform-driven work records the reserved system principal, so every audit record names an actor.
Trace ID
W3C trace id, for correlating this operation with the traces and log lines of the request that caused it. Empty when the operation ran with no trace context — a scheduled or event-driven action rather than a request.
Example
{ "operation_type": "REGISTRY_OPERATION_TYPE_UNSPECIFIED", "status": "REGISTRY_OPERATION_STATUS_UNSPECIFIED", "scope_type": "REGISTRY_SCOPE_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" } ]}