Compositions from DevKit

ltinteg-devkit vw manages virtual workflow definitions (compositions) as files in a repo. DevKit is a thin proxy: it sends your local catalog with the Bearer token; validation, persistence, and RBAC run on the Workflow API.

See Virtual workflows for the composition model.

ltinteg-devkit vw validate --target deployment-notification-send
ltinteg-devkit vw validate --all
ltinteg-devkit vw plan
ltinteg-devkit vw import              # save drafts (server fetches from GitHub)
ltinteg-devkit vw import --release    # also activate manifest.active versions
ltinteg-devkit vw promote --target deployment-notification-send

Commands read catalog.json (inventory) and optional manifest.json (desired active versions) from --dir (default .). import identifies the repo by a synced github_repository_uuid or github_connection_uuid + owner/name.

{
  "repo": {
    "github_connection_uuid": "…",
    "repository": "acme/workflows",
    "ref": "main"
  },
  "definitions_path": "definitions",
  "active": { "deployment-notification-send": "1.0.0" }
}

Set workflow_api_base_url when the Workflow API is not the same host as the core API (the default is https://workflow-api.orkestia.dev).