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

Get Retention Policy

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

Returns a retention policy by unique ID.

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
workspace
required
string
engine
required
string
id
required
string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

A retention policy controls automatic garbage-collection of artifacts in a workspace registry — e.g. “keep the last 10 tags matching v*, plus anything tagged in the last 30 days”. Retention runs project-wide on the backend, so a retention policy is scoped to the whole workspace.

object
id
stringOutput only
workspace_id

The workspace this retention policy applies to.

stringOutput only
engine

The provider this retention policy applies to.

string format: enum Output only
Allowed values: ENGINE_UNSPECIFIED ENGINE_QIBDO
rules
required

The retention rules evaluated on each run.

Array<object>
object
keep_last_n
integer format: int32
keep_newer_than

Keep artifacts newer than this age.

string
/^-?(?:0|[1-9][0-9]{0,11})(?:\.[0-9]{1,9})?s$/
keep_tag_pattern
string
schedule

A cron-style schedule string controlling when retention runs.

string
enabled

Whether the policy is active.

boolean
create_time
string format: date-time Output only
update_time
string format: date-time Output only
Example 
{
  "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"
    }
  ]
}