Declare a metadata schema
POST/v1/projects/:project_id/metadata-schemas
Declares what metadata must satisfy for one resource type under one selector. A document is selected by path_prefix, matched on a path boundary: /reports covers /reports/q1.txt and never /reports-archive/q1.txt.
The schema is compiled here, so one JSON Schema cannot parse is refused rather than stored — a stored one would be a rule that silently governs nothing. One selector has one schema per resource type; a second declaration of the same one is 409 NAME_CONFLICT. The reserved root /.system cannot be governed: a platform-written document carries no caller metadata.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 409
- 413
- 429
- 500
- 502
- 4XX
The declaration
Bad Request — unknown resource_type, a missing or unusable selector, the reserved root, or a schema that is not valid JSON Schema
Unauthorized
Forbidden
The project does not exist or the caller is not a member of it (RESOURCE_NOT_FOUND).
Conflict — this selector is already declared for this type
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there