Skip to content
Proud to collaborate with Microsoft for Startups

apphost.addon.status ​

Live Buzz status for a claimed AppHost site: transport (relay Ready), persistence (Machine / AppData state), and whether the identity app has an end-user agent bound. Redis and MinIO are ClusterIP. The Buzz host is not probed over the public internet. No kubeconfig. No secrets.

Read Buzz Deployments and pods. Customer status is cluster Ready.

Overview ​

PropertyValue
Workflow typeDag
LibraryApp-apphost
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
site_uuiduuidYes—Claimed AppHost site
addonstringNobuzz—

Output Schema ​

FieldTypeRequiredDefaultDescription
site_uuiduuidNo——
addonstringNo——
resolvejsonNo——
deploymentsjsonNo——
podsjsonNo——
appdatajsonNo——
summaryjsonNo——
ackjsonNo——
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
compensation_triggerjsonNo——
comp_queuejsonNo——
comp_current_layerjsonNo——
comp_retry_countjsonNo——

DAG Layers ​

#LayerStepsCompensation
1resolveapphost.addon.resolveapphost.web.ack
2observekubernetes.deployment.list, kubernetes.pod.listapphost.web.ack
3appdataappdata.instance.statusapphost.web.ack
4summarizeapphost.addon.status-summarize—

Execution Flow ​

Compensation ​

When any layer fails, its compensation steps run in reverse order to roll back the work completed so far.

Sub-workflows ​

Sub-workflowStep name
apphost.addon.resolveresolve
kubernetes.deployment.listdeployments
kubernetes.pod.listpods
appdata.instance.statusappdata
apphost.addon.status-summarizesummary
apphost.web.ackack

Outcomes ​

OutcomeTypeDescriptionState Data Keys
readSUCCESSBuzz status returnedapplied, cluster_ready, transport_ready, appdata_state, agent_bound
failedFAILUREApphost workflow failedfailure_reason

API Usage ​

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

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