Create a pull-through cache rule
Images pulled from /// are fetched from the upstream on first pull, with the credentials in credentialSecret, and stored in the project. Checked as registry.cacheRules.create on the rule's prospective resource name. The secret needs a grant to the rule (consumer registry, consumerResource the rule's resourceName, version latest), made by the caller in Secrets. 409 conflict when the prefix is another rule's, still being deleted, or a live repository's scope, and when the project has 25 rules.
https://registry-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/pull-through-cache-rulesAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
201
The rule, created.
400
invalid_request (with issues), invalid_cursor, or the endpoint's own 400 codes.
403
access_denied: the caller's policies don't allow the action; forbidden_origin: a cookie-authenticated write from an origin that isn't allowed; spend_limit_reached.
404
not_found: unknown, malformed, or in an organization the caller isn't in.
409
quota_exceeded (an allocation quota, with quota), idempotency_conflict, idempotency_in_progress (with Retry-After), organization_deletion_pending, operation_in_progress, or the endpoint's own 409 codes.
413
payload_too_large: the body is over the endpoint's limit (1 MiB unless it says otherwise).
429
too_many_requests, with Retry-After; or quota_exceeded (a rate, usage or concurrency quota, with quota), never with Retry-After.
500
internal_error: a bug; the details are in the logs, under the request ID.