Grant an EZGH product access to a secret
Lets one product (consumer) read the secret for one of its resources (consumerResource, a resource name in the secret's organization of a type that product uses secrets for). version is "latest" (default) or a number. Needs secrets.grants.create and secrets.versions.access on the secret, so nobody can grant more than they could read. A second grant for the same consumer and resource is 409 grant_exists; while grants are switched off the answer is 409 grants_unavailable. Uses an Idempotency-Key.
https://secrets.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/secrets/{secretId}/grantsAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
201
The new grant.
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.