Cancel an in-flight build.
curl --request POST \ --url https://stratum.example.com/v1/projects/example/compute/image-builds/example/actions/cancel \ --header 'Authorization: Bearer <token>'Flags the build; the reconciler finishes the step in flight, terminates the throwaway and marks it canceled. 409 INVALID_STATE once terminal. Gated on compute:CancelImageBuild.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Responses
Section titled “Responses”The build with cancelRequested.
One build of a recipe (ib-…), the desired-state
row the image-builder reconciler drives: pending → launching → provisioning → testing → imaging → distributing → succeeded | failed | canceled on a
throwaway instance tagged stratum.dev/image-build=<id> that is always
terminated (instanceGone is the observation that it is).
object
The image the base resolved to at launch.
The throwaway build instance.
One step’s or test’s recorded outcome. The full output is in the project’s Logs (group image-builder, stream = the build id); the row keeps the last 4 KiB as outputTail.
object
Set when the step could not run at all (agent unavailable, timeout).
Tags the step discovered for the output image: every stratum-image-tag: <key>=<value> line in its output (valid, non-reserved keys only). Laid over the recipe’s output.tags at create-image, later steps winning.
object
One step’s or test’s recorded outcome. The full output is in the project’s Logs (group image-builder, stream = the build id); the row keeps the last 4 KiB as outputTail.
object
Set when the step could not run at all (agent unavailable, timeout).
Tags the step discovered for the output image: every stratum-image-tag: <key>=<value> line in its output (valid, non-reserved keys only). Laid over the recipe’s output.tags at create-image, later steps winning.
object
Per-target results of the roll.
One distribution target’s outcome, written the moment it lands. Exactly
one of launchTemplateId / autoScalingGroupId is set; error carries
a refusal (the build still succeeded).
object
Why the build is not progressing, in whatever sense applies: on a failed or canceled build, why it ended; on a succeeded one, how many distribution targets were refused; and on a build still in flight, the converge refusal it is currently retrying — a full compute.images.count, an unreachable backend. Cleared when the build gets through or changes phase, so a value here is always live.
Example
{ "phase": "pending", "steps": [ { "kind": "cloudInit", "status": "pending" } ], "tests": [ { "kind": "cloudInit", "status": "pending" } ], "trigger": "manual"}Authenticated but not authorized.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Resource not found.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}Conflicting state.
object
The findings of a rejected IAM policy document (custom and resource policies).
One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.
object
The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.
Index of the statement at fault; -1 for the document as a whole.
The offending action, where one is at fault (ACTION_NOT_APPLICABLE).
Field errors, for codes that carry them: each problem at its field
(see FieldError). Documented on the responses that set it, e.g.
approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED.
Absent otherwise.
One field’s problem, the stage-2 installer API’s shape.
field is the field’s path, message what is wrong with it.
object
The field’s path, e.g. links[0].interface, disks[1].confirm,
mgmt.address or role; empty for the whole request.
Structured facts about the refusal, for codes that carry them. The
shape is fixed per code and documented on the response that answers
it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and
IMAGE_IN_USE. Absent for codes that carry none.
object
Example
{ "issues": [ { "code": "ACTION_NOT_APPLICABLE", "action": "compute:CreateVpc" } ]}