Operations

Bootstrap

Build produces integrate.svc; run it with -f .integrate.yaml. Ports and TLS are chassis-managed. Integration bundles arrive per tenant through meta; the block’s own entity schema is embedded and applied through the data layer.

integrate.svc -f .integrate.yaml

Boot configuration

The dispatch routes forward to two sibling blocks, wired as message clients in the boot config:

name: integrate
host: 0.0.0.0
port: "8080"
message:
  client:
    notify:                     # → the Notifications block
      protocol: rest
      name: notify
      url: https://notify.internal
      timeout: 30s
    workflow:                   # → the Workflows block
      protocol: rest
      name: workflow
      url: https://workflow.internal
      timeout: 30s
loadtenants: []                 # tenants to warm at start

Per-tenant DB pools and datastores come from the tenant config plane. Secrets referenced in connector definitions resolve through Vault.

Reloading integrations

Editing an integration bundle in the product repo (or the connector, entity, or template files inside it) takes effect on the tenant’s next meta refresh. To force a reload immediately, invalidate the tenant’s cache: DELETE /superadmin/tenant/:tenant/cache (superadmin).

Health

GET /health, GET /ready. Supervised deployments run it as service integrate with default state up.

Dependencies

config (boot + tenant config), meta (integration bundles), IAM (JWT), data (entities), Vault (connector secrets), and — for dispatch — Notifications and Workflows.