Add a version to a secret
Either the whole new field set (fields), or a base version with set and remove applied (base may be "latest"), so a rotation can change one field without reading the others. Removing a field that isn't in the base is 400; a base that doesn't exist or was destroyed is 404, and one destroyed while the write was in flight is 409 conflict, as is a version written concurrently: retry. The body may be up to 16 MiB. The response is the new version's metadata, never a value.
https://secrets.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/secrets/{secretId}/versionsAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
One of the following:
- object
- object
Returns
201
The new version.
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.
412
precondition_failed: If-Match doesn't name the secret's current ETag. Read it again and retry.
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.