repligit.appliance.launch

Launch a durable Repligit Git appliance on a customer Kubernetes cluster

Overview

Property	Value
Workflow type	Atomic
Library	App-repligit
Version	1.0

Input Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	Yes	—	CloudConnection UUID for the target Kubernetes cluster
image	string	Yes	—	Repligit container image reference (registry/repo:tag)
namespace	string	No	—	Target namespace, created if missing (default repligit)
name	string	No	—	Appliance name — DNS label (default repligit)
audience	string	No	—	JWT audience the appliance enforces (default repligit-<namespace>-<name>)
storage_size	string	No	—	Data PVC size (default 10Gi)
storage_class	string	No	—	PVC storageClassName (cluster default when unset)
service_type	string	No	—	Service type: ClusterIP
timeout_seconds	integer	No	—	Rollout wait budget in seconds (default 300)

Output Schema

Field	Type	Required	Default	Description
endpoints	json	No	—	Git and console URLs (internal DNS; node ports / LB when applicable)
applied	json	No	—	kind/name entries the manifest sync applied
audience	string	No	—	JWT audience to use with repligit.credential.mint
namespace	string	No	—	—
name	string	No	—	—
image	string	No	—	—
connection_uuid	uuid	No	—	—
service_type	string	No	—	—
storage_class	string	No	—	—
storage_size	string	No	—	—
timeout_seconds	integer	No	—	—
failure_reason	string	No	—	—
failure_type	string	No	—	—
failed_action	string	No	—	—
failed_at_state	string	No	—	—
failed_step	string	No	—	—
failed_layer	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—

States

State	Initial	Terminal	Success	Auto-advance	Description
pending	Yes	No	—	execute	—
completed	No	Yes	Yes	—	—
failed	No	Yes	No	—	—

State Diagram

Transitions

From	Action	To	Description
pending	execute	completed	—
* (any state)	fail	failed	—

API Usage

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

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