IAG 5.4.0 | Itential

IAG 5.4.0 is a minor release that expands operational visibility, automates runtime environment lifecycle management, and extends gateway clusters as the execution engine for integration HTTP requests — alongside targeted improvements for Python service authors and operators managing multi-cluster deployments.

Featured improvements

Inspect cluster commands

Two new iagctl commands give operators real-time visibility into gateway cluster state before performing maintenance. iagctl inspect cluster health checks whether the gateway store and all registered runner nodes are reachable. iagctl inspect cluster activity returns a snapshot of all currently running and recently completed work across every runner node. Both are also available as workflow tasks from the GatewayManager collection in the canvas task palette.

For more information, see Monitor cluster health and activity.

Virtual environment pruning

IAG 5.4 automates lifecycle management for Python virtual environments on gateway runner nodes. A background pruner removes idle environments on a configurable schedule, eliminating manual cleanup as deployments scale. Pruning applies to environments created by both Python script services and the runCode task.

For more information, see Python virtual environments.

Python service boolean flag support

Boolean flag arguments using argparse’s action='store_true' pattern are now fully supported in IAG 5 Python script services. Pass flags using bare --set key syntax rather than --set key=value.

For more information, see Boolean properties in Python script services.

CLI config file profiles

iagctl now supports multiple named connection profiles in gateway.conf, letting operators switch between gateway cluster connections with a single --profile flag. Existing configurations require no changes.

For more information, see Configure client profiles.

Integration execution on gateway

Gateway clusters now serve as the execution engine for integration HTTP requests, routing outbound API calls through IAG runner nodes rather than directly from Platform. This enables network-proximate execution and adds explicit proxy support for environments where outbound traffic must traverse a corporate proxy. Proxy settings are configured in Admin Essentials and inherited by all integrations by default, with per-integration overrides available.

For more information, see Execution engine.

Requirements

Platform 6.4 or later

Extended OpenTofu support

iagctl create service opentofu-plan now accepts a --backend-config flag for specifying remote state backend configuration at service creation time, enabling teams to manage infrastructure state in remote backends such as S3, Azure Storage, and Consul.

For more information, see iagctl create service opentofu-plan.