Skip to content
Proud to collaborate with Microsoft for Startups

apphost.addon.resolve ​

Resolve a claimed AppHost site to its namespace and the platform Kubernetes connection for Buzz manage verbs.

Resolve a claimed site to the controller connection and namespace.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-apphost
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
site_uuiduuidYes—Claimed AppHost site
addonstringNobuzz—
workflow_run_idstringNo—Engine-stamped parent run id when this runs as a DAG step (buzz.space.enable/delete)

Output Schema ​

FieldTypeRequiredDefaultDescription
site_uuiduuidYes——
organization_uuiduuidNo——
machine_uuiduuidNo——
machine_modestringNo——
machine_statusstringNo——
slugstringYes——
hoststringYes——
hostsjsonNo——
urlstringYes——
namespacestringYes——
addonstringYes——
connection_uuiduuidYes——
restore_ingressjsonNo——
identity_app_uuiduuidNo——
appdata_scopesjsonNo—identity_app_uuid list for the AppData status fan-out (empty without an app)
workflow_run_idstringNo——
failure_reasonstringNo—Engine-stamped failure reason
failure_typestringNo—Stable failure classification
failed_actionstringNo—Action that failed
failed_at_statestringNo—State when the workflow failed
failed_stepjsonNo—Failed DAG step envelope
failed_layerjsonNo—Failed DAG layer envelope
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

Outcomes ​

OutcomeTypeDescriptionState Data Keys
resolvedSUCCESSAddon target resolvednamespace, host
failedFAILUREApphost workflow failedfailure_reason

API Usage ​

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

{
  "workflow_type": "apphost.addon.resolve",
  "initial_data": {
    "site_uuid": "value"
  }
}