DevOps and GitOps for managed file transfer with SFTPPlus MFT

Keep SFTPPlus MFT deployments reviewable: define services and transfers in an .INI file, script administration with admin-shell, and install on Kubernetes with Helm.

Abstract blue banner illustrating Workday ERP integration

SFTPPlus MFT combines file transfer servers and automated transfers with configuration and administration suited to DevOps and GitOps workflows. Teams can review configuration alongside infrastructure changes, automate administrative work, and install the software on Kubernetes using Helm. This gives them managed file transfer capabilities without building a separate application for each exchange.

Keep configuration as code ​

SFTPPlus stores its configuration in a plain text .INI file. The same file defines services, transfers, users, and event handlers, so an application change can be reviewed together with its deployment resources. Keep the file in version control according to your organization's security policy, then promote reviewed changes through development, test, and production environments.

Configuration management tools such as Ansible and CloudFormation can install the file alongside the application. Container platforms can supply it through their standard configuration resources, including Kubernetes ConfigMaps. Credentials and other sensitive values should remain in the secret management system used by your deployment platform.

Automate administrative operations ​

The admin-shell command-line tool supports repeatable configuration and management operations from scripts, deployment pipelines, and remote terminals. It communicates with SFTPPlus through JSON-RPC and uses the same secure administrator login and role-based access controls as Web Manager.

Use the CLI when a pipeline needs to apply or inspect a management change on a running instance. Use the .INI file when the complete desired configuration should be deployed as a reviewed artifact.

Use a GitOps workflow ​

A GitOps repository can hold the SFTPPlus .INI configuration together with the deployment resources for each environment. A typical change is proposed through a pull request, reviewed by the responsible teams, and applied by the existing deployment controller after approval. The repository history then records which configuration was intended for each deployment.

This approach works for virtual machines and containers. For Kubernetes deployments, the SFTPPlus Helm chart provides an installation option that fits into an existing Helm deployment workflow. Teams can review the chart configuration along with the ConfigMaps and Secret references used by the deployment. For an orchestrated deployment, see the Kubernetes and OpenShift platform page.

Promote reviewed updates ​

DevOps teams can pin the required SFTPPlus MFT version, review the release notes, and promote an update through the same pipeline used for configuration changes.

Connect monitoring and workflows ​

SFTPPlus records file transfers and administrative actions in its audit logs. Its event handlers can send selected events to external HTTP endpoints or existing monitoring and notification services. For container log collection, a standard output handler can write selected events in Logfmt format; audit log files can also use text, CSV, or Logfmt. These integrations allow operations teams to observe file transfer activity using the same systems that monitor the rest of their infrastructure.

For process health, Prometheus monitoring provides resource usage, process start time, application metadata, and event loop delay. Teams can use these measurements in dashboards and alerts alongside the audit logs used to investigate individual transfer results.

Why choose SFTPPlus MFT for a DevOps workflow ​

Compared with maintaining scripts for each file exchange, SFTPPlus MFT keeps transfer settings, retries, and audit events in one managed application. The .INI file, authenticated CLI, and Helm installation path let teams operate that application with their existing repositories and deployment pipelines. This is useful when evaluating file transfer software for infrastructure as code: both the transfer behavior and the deployment can be reviewed before they reach production.

Request a trial to test a deployment with your configuration and file transfer workflow.