Skip to content
Proud to collaborate with Microsoft for Startups

deploy.release.start ​

Create a DeploymentRelease + DeploymentRollout for a target and dispatch the appropriate strategy workflow. Rejects with target_busy if another rollout is active.

Start a release against a DeploymentTarget by dispatching the right strategy.

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-deployments
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
deployment_target_uuiduuidYes——
image_tagstringYes—Container image tag to deploy. Substituted into target.image_template.
strategy_overridestringNo—Override target.default_strategy (immediate
source_typestringNo—Where the release came from (manual
source_refstringNo—Git ref / release tag if known. Defaults to image_tag.
commit_shastringNo——
build_metadatajsonNo—Free-form metadata stored on DeploymentRelease.build_metadata.
runtime_overridesjsonNo—Cloud Run runtime overrides forwarded to the strategy child.
secretslistNo—Cloud Run runtime secret requirements forwarded to the strategy child.
canary_policyjsonNo—Cloud Run canary stages, health checks, and rollback policy.
stable_revisionstringNo—Cloud Run stable revision used for canary traffic splits.
auto_rollbackbooleanNo—Override canary auto-rollback behavior.

Output Schema ​

FieldTypeRequiredDefaultDescription
deployment_target_uuiduuidNo——
image_tagstringNo——
strategy_overridestringNo——
source_typestringNo——
source_refstringNo——
commit_shastringNo——
build_metadatajsonNo——
runtime_overridesjsonNo——
secretslistNo——
canary_policyjsonNo——
stable_revisionstringNo——
auto_rollbackbooleanNo——
release_uuiduuidNo——
rollout_uuiduuidNo——
strategystringNo——
strategy_workflow_typestringNo——
child_workflow_uuidstringNo——
imagestringNo——
poll_attemptsintegerNo——
timed_out_atstringNo——
completed_atstringNo——
failed_atstringNo——
failed_at_statestringNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—dispatchRelease request accepted; will dispatch strategy
waitingNoNo——Polling the strategy sub-workflow
completedNoYesYes—Release completed; DeploymentRelease.status = PUBLISHED
failedNoYesNo—Release failed; DeploymentRelease.status = FAILED

State Diagram ​

Transitions ​

FromActionToDescription
pendingdispatchwaitingLock target, create release+rollout, start strategy
waitingpollwaitingRe-poll while the strategy is still running
waitingcompletecompletedStrategy reached terminal-success
* (any state)failfailedLifecycle moves to failed

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "deploy.release.start",
  "initial_data": {
    "deployment_target_uuid": "value",
    "image_tag": "value"
  }
}