Gateway configuration import and export

Gateway Manager 1.1.1+

Gateway Manager exposes Itential Gateway’s configuration import and export capabilities through a UI and the Platform API. You can use either method to move configurations between gateway instances, seed new environments, and automate pipeline-driven deployments—without embedding the iagctl CLI tool in your workflows.

How it works

Gateway Manager exposes import and export through the Platform API. You can trigger configuration imports and exports from your CI/CD pipelines using standard API calls, the same way you call other Platform endpoints. Both are also available as workflow tasks from the GatewayManager collection in the canvas task palette.

The Gateway Manager UI also provides import and export actions directly from the cluster list, giving platform administrators a way to manage configurations without writing pipeline code.

You can also import and export configurations using the iagctl CLI tool. See iagctl db import and iagctl db export.

Use cases

Pipeline promotion (dev → stage → prod)

Store your configuration files in source control alongside your services and playbooks. As you promote across environments, call the Platform API import endpoint from your pipeline to push updated configurations into each gateway instance.

Container and Kubernetes bootstrap

Instead of invoking iagctl to seed an initial configuration at startup, call the Platform API import endpoint from your initialization logic or Helm chart to load configurations when a gateway comes online.

Ad hoc configuration management

Use the Gateway Manager UI to import or export configurations interactively without building a pipeline integration.

Supported formats

MethodImport formatsExport formats
UIJSON, YAMLJSON, YAML
Platform APIJSONJSON
iagctlYAMLJSON, YAML

Important: gateway connection requirement

A gateway must be connected and active in Gateway Manager before you can import a configuration. You can’t trigger an import during cluster creation or before the gateway establishes an active connection. The UI disables the import action for gateways that aren’t active.

Plan your pipeline to call the import endpoint only after confirming the gateway is connected and active.