Connect a warehouse to a bucket, a Kafka cluster or a database
Asynchronous. The credential on the target is made as the caller: objects.buckets.update on a bucket; hostedqueues.users.create on a Kafka cluster or databases.users.create on a database, and secrets.secrets.create for its Secret. A Kafka cluster or database must be in the warehouse's VPC (400 target_not_in_vpc); a database is PostgreSQL, Percona or MariaDB (400 unsupported_target); a target that refuses the credential as invalid, such as a logical database it hasn't got, is 400 target_refused.
https://warehouse-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/warehouses/{warehouse}/connectionsAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
Returns
202
The operation, which Location names; poll it until it finishes.
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.