Skip to content
Proud to collaborate with Microsoft for Startups

repligit.appliance.status ​

Read the state of a launched Repligit appliance

Read the state of a Repligit appliance launched by repligit.appliance.launch.

Inputs:

  • connection_uuid: kubernetes CloudConnection (required)
  • namespace: appliance namespace (default repligit)
  • name: appliance name (default repligit)

Outputs (terminal state_data):

  • ready: deployment has its replica available
  • replicas / ready_replicas: desired vs available
  • data_volume_phase: PVC phase (Bound/Pending/absent)
  • endpoints: git/console URLs (internal DNS; node ports / LB when applicable)
  • image: currently deployed image reference

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-repligit
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
connection_uuiduuidYes—CloudConnection UUID for the target Kubernetes cluster
namespacestringNo—Appliance namespace (default repligit)
namestringNo—Appliance name (default repligit)

Output Schema ​

FieldTypeRequiredDefaultDescription
readybooleanNo—Deployment has its replica available
replicasintegerNo—Desired replicas
ready_replicasintegerNo—Available replicas
data_volume_phasestringNo—Data PVC phase (Bound/Pending/absent)
endpointsjsonNo—Git and console URLs
imagestringNo—Currently deployed image reference
namespacestringNo——
namestringNo——
connection_uuiduuidNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

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

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

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

{
  "workflow_type": "repligit.appliance.status",
  "initial_data": {
    "connection_uuid": "value"
  }
}