Replace a group's launch spec and start a release
Asynchronous: answers 202 with the UpdateAutoscalingGroupLaunchSpec operation, which ends when the release does. The version moves on, the image is resolved again and pinned, and a release in progress is superseded (its operation ends cancelled). 409 operation_in_progress while the group is still being created. 503 unavailable (with Retry-After) while autoscaling is unavailable in the region; nothing changes.
https://compute-api.ezghcloud.com/v1/organizations/{orgId}/projects/{projectId}/autoscaling-groups/{group}/launch-specAuthorization
Path parameters
Header parameters
Request bodyJSONrequired
- botoptionalstring
A Bot of the organization (its bot_ ID) to attach: code on the instance gets short-lived API keys acting as it from the metadata service. Needs bots.pass on the Bot (403 access_denied naming bots.pass). An unknown Bot or a UUID is 400 invalid_request at bot.
pattern: ^bot_[a-z0-9]{12}$
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.
412
precondition_failed: the group changed since the ETag in If-Match was read.
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.