Port Workflows with JSON, Terraform, and Pulumi
On this page
Quick answer
Use JSON for the portable workflow definition, Terraform or Pulumi when workflow lifecycle belongs in infrastructure review, and the editor for rapid visual inspection. Port documents trigger, input, action, AI, condition, approval branch, validation, connection, and output-passing patterns in its IaC surface.
Choose one source of truth. Do not let editor changes and IaC apply compete without a drift policy.
Review checklist
Version node identifiers, connections, input and output schemas, permissions, approver resolution, integration references, secrets, provider and model selection, retries, timeouts, and failure behavior. Validate graph reachability and ensure every branch terminates with an explicit outcome.
In CI, parse and validate the workflow, plan the diff, run representative cases, block destructive permission expansion, and require review from workflow and platform owners. After apply, compare the live definition with the committed artifact and preserve a known-good rollback version.
Use the human approval guide for approval branches and the GA guide for rollout.
Official sources
Source check: August 23, 2026. Verify current provider resources, schema, node support, imports, drift behavior, and account permissions.