Skip to main content

Communication Services

Commands for managing adapters, pipelines, pipeline triggers, pools, and data flows.

DisableCommunication is refused while any pool or workload of the tenant is still deployed — undeploy them first with UndeployWorkload and UndeployPool (see Tenant Lifecycle).

  • Adapters — external clients that connect to OctoMesh and execute data pipelines; reference for the GetAdapters, DeployAdapter, and GetPipelineSchema commands here.
  • Pipeline Triggers — scheduled pipeline executions based on cron expressions; concept behind DeployTriggers and UndeployTriggers.
  • Pools — group managed devices and their adapters together for orchestrated deployment; concept behind GetPools, DeployPoolAdapters, and UndeployPoolAdapters.
  • DataFlows & Pipelines — pipelines plus their triggers grouped into deployable units; concept behind DeployDataFlow, UndeployDataFlow, GetDataFlowStatus, and the pipeline-level commands (DeployPipeline, ExecutePipeline, GetPipelineStatus, etc.).
  • On-Demand Lifecycle (Scale-to-Zero) — idle adapters scale to zero replicas and wake on demand; concept behind SetCommunicationLifecycle and GetCommunicationLifecycle.