Skip to main content
PATCH
Update repository settings
Primary IAM action: registry:UpdateRepository. Requests containing non-null tags with neither tag_mutability nor deletion_protection set require registry:TagResource instead of registry:UpdateRepository. Other updates require registry:UpdateRepository. See REGISTRY permissions for policy examples.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Path Parameters

repository_id
string<uuid>
required
Example:

"a1b2c3d4-5e6f-4a7b-8c9d-0e1f2a3b4c5d"

Body

application/json

Omitted fields are left alone. tag_mutability and deletion_protection are therefore distinguishable from false only by absence, which is why a request that changes nothing but tags is authorized as registry:TagResource.

tag_mutability
enum<string>
Available options:
mutable,
immutable
deletion_protection
boolean
tags
object

Response

Repository updated.

repository
object
required
push_commands
string[]

The login/build/push sequence for this repository. Rendered server-side because the login username, the endpoint, and the account handle's position in the reference all come from service configuration.

Example: