Integration lifecycle management (ILM) is the version control and release management system for integrations in integrator.io. Use ILM to clone an integration, move updates from development to production with pulls and merges, and roll back with snapshots and reverts. ILM records each snapshot, pull, and revert as a revision.
Use a non-production environment for ILM workflows. If you see Production and Sandbox in integrator.io, your account uses the legacy environment structure. See Developing with integration lifecycle management.
Key concepts
ILM revolves around six concepts. Each link opens the article that explains it, and Integration lifecycle terminology defines every term.
- Revision — The record integrator.io creates each time you take a snapshot, pull, or revert. See Work with revisions.
- Snapshot — A backup of an integration's state. See Back up an integration with a snapshot.
- Clone — A directly related copy of an integration that you change without affecting the original. See Clone an integration for Integration Lifecycle Management (ILM).
- Pull — A comparison and merge of changes from a remote integration into your current integration. See Pull changes from one integration to another.
- Revert — A rollback to an earlier revision. See Revert changes.
- Current and remote integrations — The integration you open and create the pull from is always the current integration, so you can pull in either direction between an integration and its clone. In a standard workflow, the current integration is production and the remote integration is a development clone.
Standard clone-and-pull workflow
- Clone the integration into a non-production environment to create an independent working copy. See Clone an integration for Integration Lifecycle Management (ILM).
- Make and test changes in the clone.
- Create a pull to compare the clone's changes with the production integration. See Pull changes from one integration to another.
- Review the changes, resolve any conflicts, and merge the pull. See Pull changes from one integration to another.
When the merge completes, integrator.io records a completed pull revision that you can revert to. See Revert changes.
For example setups of integrations and clones, see Developing with integration lifecycle management.
When to use ILM
Use ILM when:
- You need to test integration changes before they reach production.
- Multiple developers or teams work on the same integration and need to coordinate changes.
- You maintain a mission-critical integration where an unexpected change carries significant business risk.
- You want a reliable rollback point before you make major changes to a live integration.
- Your organization follows a software development lifecycle with separate development, QA, and production stages.
Skip ILM when you're the only developer on a simple integration that rarely changes. Cloning and pulling can add more overhead than value. Create a snapshot before each change instead.
To check which integrations and resources ILM supports, see ILM supported resources and limits.